-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fileparser2 #26
Fileparser2 #26
Conversation
…rule class is defined, #17 documentation is started. Ruff check and black check completed.
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | OpenSSH Private Key | 3b46c30 | testmodule/�� | View secret |
- | OpenSSH Private Key | 55a4717 | testmodule/�� | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General changes:
- add type hints for all function arguments and return values. You already list the argument types in the function docstrings which is great! In the latest Python versions it is usually recommended to define them as type hints which should be enough, you can remove them from the docstrings.
- remove the example files in the
files
directory but keep a select few (maybe 5 files) that you think are interesting
|
||
- name: Run Python script on JOB files | ||
run: | | ||
find . -name "*.JBI" -exec python testmodule/fileparser.py {} \; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you have implemented that user can pass a folder as argument, why not use that command instead of the complex bash syntax?
README2.md
Outdated
### Installation | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Installation should list how to install the python package, e.g. pip install .
README2.md
Outdated
from testmodule import JobFile | ||
|
||
JobFile(`EXAMPLE_FILE.JBI`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The user guide section should answer the following question:
- How to I check the rules for a single
.JBI
file? - How do I check the rules for all files in a folder?
Co-authored-by: Çağtay Fabry <cagtay.fabry@bam.de>
#18 rule defined, #20 rule defined,
#14 rule formatting completed,
#22 rule class is defined,
#17 documentation is started.
Ruff check and Black check completed.