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

Tweak Trigger: labels #42452

Merged
merged 8 commits into from
Mar 16, 2023
Merged

Tweak Trigger: labels #42452

merged 8 commits into from
Mar 16, 2023

Conversation

chadwhitacre
Copy link
Member

@chadwhitacre chadwhitacre commented Dec 19, 2022

Two changes:

  1. Observe the Foo: Bar pattern. Use the aliases feature to rename. "For example, given the following config, GitHub Label Sync will look for labels on GitHub named either 'feature' or 'enhancement' then update them to match the newer config rather than deleting them."

  2. Standardize colors. I recently introduced a Sync: Jira label, which seems loosely related to Trigger: . I propose using the same color for both types.

@chadwhitacre chadwhitacre requested a review from a team as a code owner December 19, 2022 20:02
@github-actions
Copy link
Contributor

github-actions bot commented Dec 19, 2022

🏷 The following changes will be made to the repository labels

Validating provided labels
Fetching labels from GitHub
 > Changed: the "trigger-getsentry-external" label in the repo is out of date. It will be updated to "Trigger: getsentry tests" with color "#A0CABD" and description "once code is reviewed: apply label to PR to trigger getsentry tests".
 > Changed: the "Trigger: Revert" label in the repo is out of date. It will be updated to "Trigger: Revert" with color "#A0CABD" and description "add to a merged PR to revert it (skips CI)".
 > Added: the "python" label in the repo is not expected. It will be deleted.
This is a dry run. No changes have been made on GitHub

@evanpurkhiser
Copy link
Member

Good stuff, but whatever listens for this trigger will also need updated yes?

.github/labels.yml Outdated Show resolved Hide resolved
Co-authored-by: Evan Purkhiser <evanpurkhiser@gmail.com>
@chadwhitacre
Copy link
Member Author

whatever listens for this trigger will also need updated yes?

Good call. Putting this in draft while I chase that down.

Any pointers, @asottile-sentry?

@chadwhitacre chadwhitacre marked this pull request as draft December 19, 2022 21:33
@chadwhitacre
Copy link
Member Author

@vercel
Copy link

vercel bot commented Dec 19, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
sentry 🔄 Building (Inspect) Dec 19, 2022 at 10:18PM (UTC)
storybook 🔄 Building (Inspect) Dec 19, 2022 at 10:18PM (UTC)

@chadwhitacre
Copy link
Member Author

whatever listens for this trigger will also need updated yes?

Done in 07adfc8.

@chadwhitacre
Copy link
Member Author

Picked off another in getsentry/develop#795.

I believe that's it (except for sentry-test-repo, which is archived).

@evanpurkhiser
Copy link
Member

Going to let @asottile-sentry approve this one 👍

@chadwhitacre
Copy link
Member Author

We should probably pause the automation before landing this, so that the bot can update all the labels without triggering a bunch of unnecessary builds.

@chadwhitacre
Copy link
Member Author

Yeah sorry I've been sitting on this, will try to make another push soon.

@github-actions
Copy link
Contributor

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@github-actions
Copy link
Contributor

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@chadwhitacre
Copy link
Member Author

it's going to trigger a bunch of runs

Can we remove the trigger-getsentry-external label from closed PRs? That would drastically minimize the problem. Right now there's only one open PR, for example, and if we accidentally trigger a new run on one or two PRs I think that's fine?

@asottile-sentry
Copy link
Member

it's going to trigger a bunch of runs

Can we remove the trigger-getsentry-external label from closed PRs? That would drastically minimize the problem. Right now there's only one open PR, for example, and if we accidentally trigger a new run on one or two PRs I think that's fine?

yeah that'd probably work

@chadwhitacre
Copy link
Member Author

Okay, let's do it! Label cleared. Need an approval here and then I will proceed.

Copy link
Member

@asottile-sentry asottile-sentry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chadwhitacre
Copy link
Member Author

Not sure why this is failing with a syntax error. The colon is quoted. Is it something else?

if: github.event.action != 'labeled' || github.event.label.name == 'Trigger: getsentry tests'

@asottile-sentry
Copy link
Member

the whole string needs to be quoted -- otherwise yaml partially parses it as a mapping entity

@chadwhitacre
Copy link
Member Author

Like this?

@asottile-sentry
Copy link
Member

yeah that should work -- I think pre-commit run check-yaml --files .github/workflows/* will show that too iirc

@chadwhitacre chadwhitacre merged commit 174035e into master Mar 16, 2023
@chadwhitacre chadwhitacre deleted the cwlw/tweak-trigger-labels branch March 16, 2023 16:41
@chadwhitacre
Copy link
Member Author

$ pre-commit run check-yaml --files .github/workflows/* 
No hook with id `check-yaml` in stage `commit`
$

I looked through .pre-commit-config.yaml and don't find check-yaml.

@chadwhitacre
Copy link
Member Author

@asottile-sentry
Copy link
Member

hmmm weird I could have sworn we had check-yaml

chadwhitacre added a commit that referenced this pull request Mar 16, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Apr 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants