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
[ENH] ensure update-contributors
workflow does not run on main
#6181
Comments
Pinging @MEMEO-PRO and @Xinyu-Wu-0000 due to earlier comments or contributions to GHA. |
Possible solutions:
Add
Add I used sematic-release before and gained some familiarity with GHA. Just commented from vague memory though, not enough time to confirm and make a PR. |
Please, check linked PR, and give feedback |
@fkiraly please what do you mean by it does not invalidate results of the normal CI. Could you explain why it should be executed before the test workflow? |
#### Reference Issues/PRs Fixes #6181. #### What does this implement/fix? Explain your changes. This PR ensures that `Update Contributors` does not run on `main`. It also makes sure `build wheels` only triggers when `release` is triggered and and `Update Contributors` is completed.
reopening in case there is still need for discussion. |
@sammychinedu2ky, adding my explanation from #6189 here: Currently (prior to #6189), It seems that the That is, while things like Consequently, the jobs dashboard on the pull request looks like this: If the |
So currently a change push to the contribution file will also trigger the test workflow
|
Thanks for the suggestion. Since I'm not that expert with GHA, could you describe in plain English what the intended behaviour is, of the code you posted? |
This was my addition to the "normal CI" @fkiraly, I think this will be a good fix, from my understanding of the problem |
I mean, can you please describe in plain English what your proposed change is intending to do, under which condition what happens, etc? |
So this tells the runner to run the test flow either during a push when the update_contributor flow isn't running or to be triggered when the update_contributor flow runs but after it has completed it's execution. |
Questions for @Greyisheep and @sammychinedu2ky
General question: is there a way to ensure that update contributor workflow only runs in a PR of its own instead of modifying apparently random PR's (even those that don't modify all contributors file)? |
I think it will still run since a completed state is different from a successful state which you can see here For your general question, I think the update_contributor workflow only runs in a pr of its own when the contributor file is edited @yarnabrina |
This is not the case. Here are some examples:
I couldn't find where it explained what all are considered as completed state. Can you please explain in plain English? Sorry for making this request repeatedly, we are not GHA experts. |
Hi @yarnabrina
the activity type in the sample above is set to completed, Which means run the test flow once the update contribution flow is complete or when a push event to the main branch is triggered.. now you can go further to run a job in the test flow depending on the conclusion of the activity. Which could be a failure or a success. You can find that here: |
I'd wait for other @sktime/core-developers to share their opinion, but I'd prefer myself to run this workflow independently of unit tests in a complete different PR. |
Yh will be better to test independently to be sure 💯 |
(good first issue for contrinbutors with GHA experience)
The
update-contributors
workflow (which compiles theall-contributorsrc
list into theCONTRIBUTORS
page) is triggered on any branch, includingmain
.On
main
, however, it fails due to credentials, and anyway nothing should directly modifymain
.An attempt to change the trigger condition failed: #6133, this seems due to trying to push to forks, as @yarnabrina has noted and @Xinyu-Wu-0000 explains here: #6093 (comment)
It would be great if we could modify the workflow so:
main
The text was updated successfully, but these errors were encountered: