-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
feat: New SCM and pull request ApplicationSet generators for Gitea #8989
Conversation
903018b
to
680a6a1
Compare
Codecov Report
@@ Coverage Diff @@
## master #8989 +/- ##
==========================================
+ Coverage 45.00% 45.13% +0.13%
==========================================
Files 212 214 +2
Lines 25272 25407 +135
==========================================
+ Hits 11373 11468 +95
- Misses 12292 12325 +33
- Partials 1607 1614 +7
Continue to review full report at Codecov.
|
An initial implementation of Pull Request and SCM generators for Gitea. API paging, and repo labels have not been implemented. Signed-off-by: Dan Molik <dan@danmolik.com>
re-trigger linting check Signed-off-by: Dan Molik <dan@danmolik.com>
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.
Do you have time to put some test coverage on the new code?
I think mocks would be appropriate for testing generators/. For services/ we could either try to find a hosted gitea instance to rely on (like in the gitlab tests), try to spin one up in e2e tests, or just leave it untested.
I guess even the services/* files can be tested with giteaProvider and giteaService mocks. |
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.
LGTM!
Okay I just need to rebase or sign my commit |
@dmolik yep looks like the most recent 2 commits need to be signed. I think the DCO check details should have instructions for signing multiple commits. |
Yea I really should just turn auto signing on |
Signed-off-by: Dan Molik <dan@danmolik.com>
Signed-off-by: Dan Molik <dan@danmolik.com>
@rishabh625 if you're happy, I'll merge! |
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.
other than 2 comments LGTM great work
…rgoproj#8989) * feat: New SCM and pull request ApplicationSet generators for Gitea An initial implementation of Pull Request and SCM generators for Gitea. API paging, and repo labels have not been implemented. Signed-off-by: Dan Molik <dan@danmolik.com> * chore: white space in hack/test.sh re-trigger linting check Signed-off-by: Dan Molik <dan@danmolik.com> * chore: add gitea_scm and gitea_pr tests Signed-off-by: Dan Molik <dan@danmolik.com> * bug: ensure gitea scm haspath detects directories correctly Signed-off-by: Dan Molik <dan@danmolik.com> Signed-off-by: asingh51 <Ashutosh_Singh@intuit.com>
…rgoproj#8989) * feat: New SCM and pull request ApplicationSet generators for Gitea An initial implementation of Pull Request and SCM generators for Gitea. API paging, and repo labels have not been implemented. Signed-off-by: Dan Molik <dan@danmolik.com> * chore: white space in hack/test.sh re-trigger linting check Signed-off-by: Dan Molik <dan@danmolik.com> * chore: add gitea_scm and gitea_pr tests Signed-off-by: Dan Molik <dan@danmolik.com> * bug: ensure gitea scm haspath detects directories correctly Signed-off-by: Dan Molik <dan@danmolik.com> Signed-off-by: wojtekidd <wojtek.cichon@protonmail.com>
An initial implementation of Pull Request and SCM generators for Gitea.
API paging, and repo labels have not been implemented.
Signed-off-by: Dan Molik dan@danmolik.com
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: