Skip to content
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

GH-41983: [Dev] Run issue labeling bot only when opening an issue (not editing) #41986

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

jorisvandenbossche
Copy link
Member

@jorisvandenbossche jorisvandenbossche commented Jun 5, 2024

Rationale for this change

Currently the bot will remove manually added Component labels, because at that point you are editing the issue and the workflow is run again, reinstating the labels in the "Components" section in the top post created by the issue form.

Therefore, restrict this bot to only run when the issue is "opened"

@github-actions github-actions bot added the awaiting committer review Awaiting committer review label Jun 5, 2024
@assignUser assignUser merged commit 37d0acd into apache:main Jun 5, 2024
6 checks passed
@assignUser assignUser removed the awaiting committer review Awaiting committer review label Jun 5, 2024
@github-actions github-actions bot added the awaiting committer review Awaiting committer review label Jun 5, 2024
@jorisvandenbossche jorisvandenbossche deleted the gh-41983 branch June 5, 2024 14:43
vibhatha pushed a commit to vibhatha/arrow that referenced this pull request Jun 5, 2024
…ue (not editing) (apache#41986)

### Rationale for this change

Currently the bot will remove manually added Component labels, because at that point you are editing the issue and the workflow is run again, reinstating the labels in the "Components" section in the top post created by the issue form.

Therefore, restrict this bot to only run when the issue is "opened"

* GitHub Issue: apache#41983

Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Signed-off-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Copy link

After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 37d0acd.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting committer review Awaiting committer review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants