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

v1: backport workflow/label changes for semver+label #2679

Closed
wants to merge 4 commits into from

Conversation

EmilienM
Copy link
Contributor

@EmilienM EmilienM commented Jul 6, 2023

Backport of the following commits from master:

  • [CI] Drop branch filters for 'Ensure Labels' and 'CodeQL' jobs

So they can run on stable branches too.

  • Instrument backporting to v1

Add the changes to semver & labels, useful for v1 branch.
The bits around backports are removed in another commit (see below).

  • chore: Fix labels

  • Remove backport workflow & label

We don't want the backport workflow (and its labels) to exist in v1.

mandre and others added 3 commits July 6, 2023 08:39
These jobs should run on all branches, so drop the branch filter that
were in place.

For the CodeQL job, it seems like the github action syntax does not allow for a simplified `on` syntax, while at the same time using a `on.schedule`, so drop the periodic that we weren't paying attention to anyway. We have enough signal with just the PR jobs.

(cherry picked from commit 9a407d6)
The stable branch is now `v1`. Non-breaking changes will be backported
by applying a `backport-v1` label.

(cherry picked from commit b984718)
The PR gophercloud#2656 caused all
labels to be removed, because each run of the action eliminates all
labels that aren't listed.

This PR reintroduces our semver labels and the `good first issue` label
in the repository.

(cherry picked from commit d8128d3)
This isn't needed in `v1` branch.
@pierreprinetti
Copy link
Contributor

Once the backporting automation is working propertly, I'd like to let it deal with the backports. WDYT?

@github-actions github-actions bot removed the semver:patch No API change label Jul 6, 2023
@coveralls
Copy link

coveralls commented Jul 6, 2023

Coverage Status

coverage: 79.05%. remained the same when pulling ee184da on shiftstack:manual_backport into b277c7b on gophercloud:v1.

@EmilienM EmilienM added the semver:patch No API change label Jul 6, 2023
@EmilienM
Copy link
Contributor Author

EmilienM commented Jul 6, 2023

Once the backporting automation is working propertly, I'd like to let it deal with the backports. WDYT?

Do you mean you want to do the backports that I manually did, via the new automated system?
Not all backports were clean, so I'm not sure it'll work. But I'm fine either way.

on:
push:
branches:
- master
Copy link
Contributor

Choose a reason for hiding this comment

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

As Pierre pointed out the other day, this workflow syncs the repository labels from what is defined in the .github/labels.yaml file. If we were to run this from the v1 branch, we would delete the backport-v1 label each time we had a PR triggering this workflow in the v1 branch. This was my mistake and we should revert it.

Copy link
Contributor

Choose a reason for hiding this comment

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

In fact, we should even delete this workflow from the v1 branch.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm a bit confused by what we want now, I'll let @pierreprinetti comment; you seem to have a stronger opinion on what we should be doing wrt these workflows in v1 branch. Let me know if you need help with that PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

Closing in favor of #2683

README.md Show resolved Hide resolved
@mandre
Copy link
Contributor

mandre commented Jul 10, 2023

Closing in favor of #2683.

@mandre mandre closed this Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch No API change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants