-
Notifications
You must be signed in to change notification settings - Fork 151
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(gh-action): ensures generated files are up-to-date in PR #917
feat(gh-action): ensures generated files are up-to-date in PR #917
Conversation
c0b093b
to
09144d2
Compare
09144d2
to
ad6d755
Compare
/retest-required |
1 similar comment
/retest-required |
I find it inconvenient that for such PRs we have to trigger operator-specific jobs (image creation, tests). These are unrelated changes. By doing so "time to merge" takes longer for no good reason. Not to mention it has a cost. I think for everything WDYT? |
so what you mean is for changes related to .gitignore, md files etc you want the skip the ci/prow jobs right? |
|
@bartoszmajsak @ykaliuta @zdtsw : created a pr to prevent the unwanted running of prow jobs: openshift/release#49860 |
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.
That's a really helpful addition! Thanks @AjayJagan.
I have a few suggestions, mostly about naming. From the functionality perspective it's solid.
37713a3
to
a41f3a2
Compare
a41f3a2
to
7e9b6ba
Compare
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.
Sorry for ping-pong review... I missed one thing here.
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
CMD="make generate manifests api-docs" | ||
$CMD | ||
echo "CMD=$CMD" >> $GITHUB_OUTPUT |
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.
This is how I originally started, but wanted to be more fancy with fc
:) that's fine I guess, though shellcheck will freak out :)
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bartoszmajsak, zdtsw The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
A PR Comment is nice, A Commit pushed to the branch with the updated changes; priceless.. ;) |
@aslakknutsen , I wanted that power delegated to the pr creator itself 😅, that is why I chose this path. |
i just realized a funny thing: |
that is true, maybe we can create an issue in their repo asking to release an arm-supported version. |
i can build it myself, but @VaishnaviHire will bump this issue next week |
…t-data-services#917) * RHOAIENG-4433 Update readme/config files * rework gh action based on comments * feat(gh-action): ensures generated files are up-to-date in PR * fix review comments * reuse cmd
* feat(gh-action): ensures generated files are up-to-date in PR (#917) * RHOAIENG-4433 Update readme/config files * rework gh action based on comments * feat(gh-action): ensures generated files are up-to-date in PR * fix review comments * reuse cmd * fix(gen): upgrades to crd-ref-doc generator to latest version (#920) fix(gen): upgrades to crd-ref-doc to latest version - add "diff" in the failed GH action to help understand problem - update: api doc --------- Signed-off-by: Wen Zhou <wenzhou@redhat.com> * fix: Enable annotations using golangci-lint(gh action) (#919) * fix: Enable annotations using golangci-lint(gh action) * update versions * fix(make): cleans linter cache on clean (#922) When juggling between branches golangci linter cache can have leftovers from the code that does not exist in the other branch. This can lead to errors while running `make lint` as the linter tries to check cached sources first. This change cleans the linter cache as part of the clean target to ensure consistency. Here's an example of an invalid cache state leading to error: ``` WARN [runner] Can't process result by autogenerated_exclude processor: can't filter issue result.Issue{FromLinter:"ireturn", Text:"Entry returns interface (github.com/opendatahub-io/opendatahub-operator/v2/pkg/feature.DataProvider)", Severity:"", SourceLines:[]string(nil), Replacement:(*result.Replacement)(nil), Pkg:(*packages.Package)(0xc001343e00), LineRange:(*result.Range)(nil), Pos:token.Position{Filename:"/home/bartek/code/rhods/opendatahub-operator/incubation/pkg/feature/data_provider.go", Offset:1382, Line:45, Column:1}, HunkPos:0, ExpectNoLint:false, ExpectedNoLintLinter:""}: failed to get doc of file ``` * chore(Github): update issue template re-direct user for jira (#838) * chore(Github): update issue template re-direct user for jira Signed-off-by: Wen Zhou <wenzhou@redhat.com> * Update .github/ISSUE_TEMPLATE/feature_request.md Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com> * Update .github/ISSUE_TEMPLATE/bug_report.md Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com> --------- Signed-off-by: Wen Zhou <wenzhou@redhat.com> Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com> * chore: Small Makefile fixes (#928) * Go back to using `IMG ?=` rather than forcing the value with `IMG =`. This makes it easier to override the value of `IMG` for development, and it also aligns it to how `BUNDLE_IMG` is assigned. * Add `prepare` as dependency of the `undeploy` target. This is just for convenience, although when looking at the other targets, `prepare` may simply be a missing dependency in `undeploy`. Signed-off-by: Edgar Hernández <23639005+israel-hdez@users.noreply.github.com> * fix(test): pin version not latest which just introduced to use go 1.22 (#934) * fix(test): pin version not latest which just introduced to use go 1.22 Signed-off-by: Wen Zhou <wenzhou@redhat.com> * update: code review Signed-off-by: Wen Zhou <wenzhou@redhat.com> --------- Signed-off-by: Wen Zhou <wenzhou@redhat.com> --------- Signed-off-by: Wen Zhou <wenzhou@redhat.com> Signed-off-by: Edgar Hernández <23639005+israel-hdez@users.noreply.github.com> Co-authored-by: Ajay Jaganathan <36824134+AjayJagan@users.noreply.github.com> Co-authored-by: Bartosz Majsak <bartosz.majsak@gmail.com> Co-authored-by: Edgar Hernández <ehernand@redhat.com>
This is a follow up task related to https://issues.redhat.com/browse/RHOAIENG-4185
Fixes: https://issues.redhat.com/browse/RHOAIENG-4433
Description
In the ODH repository, whenever a change is made in the apis/ folder, it updates the CRDS and README(of the API). Many times devs forget to run this command and as a result, there are some mismatches in these files.
The idea is to create a gh action that will check if these updates are made properly and will prevent the merge of the PR if such a situation arises.
ref: #890 (comment)
Additionally, we may need to use
Require status checks to pass before merging
setting in GH to prevent the merge of the pr if the check does not pass.How Has This Been Tested?
To test this change
apis/
folder and don't runmake generate
ormake manifests
ormake api-docs
Merge criteria: