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

Make sure to include the v8 version in autogenerated commit and PR description #205

Merged

Conversation

GustavoCaso
Copy link
Contributor

To avoid confusion when the upgrade workflow runs, we can add the v8 version to the autogenerated PR, that way if we haven't merged one of the autogenerated PRs and the workflows runs and find a new stable version, we are going to be able to see which PR is the latest one.

Here is how the autogenerated PR looks like:
image

Ultimately, I think we could make the upgrade workflow to close any old upgrade PR that haven't been merged if a new stable v8 version is released.

@codecov
Copy link

codecov bot commented Oct 25, 2021

Codecov Report

Merging #205 (a6bbe58) into master (c82628d) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #205   +/-   ##
=======================================
  Coverage   95.59%   95.59%           
=======================================
  Files          16       16           
  Lines         545      545           
=======================================
  Hits          521      521           
  Misses         15       15           
  Partials        9        9           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c82628d...a6bbe58. Read the comment docs.

@genevieve genevieve merged commit a8894db into rogchap:master Oct 25, 2021
@GustavoCaso GustavoCaso deleted the add-version-number-to-upgrade-PR-title branch October 25, 2021 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants