-
Notifications
You must be signed in to change notification settings - Fork 65
Added the option to use configs of format templates #1229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Conventional Commits Report😢 No conventional commits found. 👉 Learn more about the conventional commits usage at Greenbone. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1229 +/- ##
=======================================
Coverage 97.78% 97.78%
=======================================
Files 73 73
Lines 5110 5112 +2
Branches 928 929 +1
=======================================
+ Hits 4997 4999 +2
Misses 76 76
Partials 37 37 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
@Chrxxxxs thanks a lot for the PR
IMHO the config_id argument was added to GMP 22.6 only and is not available for 22.4 and 22.5. I need to verify that.
Could you add tests for the report_config_id argument too and change your commit message to add argument scan_config_id for get_report to get customizable reports
?
Head branch was pushed to by a user without write access
Hi @bjoernricks, |
@Chrxxxxs could you cleanup your commits into a single commit (via git rebase -i)? |
also you need to run |
Im sorry i think i used a wrong command. I dont fully understand git yet, can i also use venv to run the test file or do i need to use poetry? |
I used poetry now to run the formatting on the test. Could you maybe try and explain the git rebase command to me? I tried using it and it just seems to make more commits instead of squashing it into one |
With git rebase you can rewrite your git history. See https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History for details. |
Yes to setup the venv. |
The Git link says that i shouldn't use this on commits that I already sent to a server. Should i open a new pull request with the changes or can i still squash my fork into 1 commit? |
That's a miss indication. Your PR is just for preparing changes. Therefore we can change and update it. |
Head branch was pushed to by a user without write access
All changes should now be in Commit d06ead1. I hope this is what you meant. |
Nope. https://github.com/greenbone/python-gvm/pull/1229/commits contains 7 commits. I would like to get a single one. You need to squash them. |
Head branch was pushed to by a user without write access
Head branch was pushed to by a user without write access
I think i got it now. Apologies for the amount of tries it took me. As i said its my first Pull Request. |
Looks good now but sadly I forgot to mention you need to remove the changes from the GMP v224 files. We only want to add that change to GMP 22.6. |
It got added again in my first force push but i think i removed it in my second, didn't i? I also saw that after looking at the online commit |
Looks good to me know. One last thing could you also add a test to https://github.com/greenbone/python-gvm/blob/main/tests/protocols/gmp/requests/v226/test_reports.py ? |
Head branch was pushed to by a user without write access
I added the test and formatted it again with poetry run black :) |
Thanks! |
What
added the option to use the config id with get_report to get customizable reports
Why
It was not possible to add a config to the format that was selected. Therefore it was only possible to use the already existing formats from Greenbone and not the custom configs to enable different fields.
This is my first contribution ever so please let me know if there are things that i missed or should do differently :)