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

docs(main): auto release node using just #2537

Merged
merged 1 commit into from
Dec 17, 2023

Conversation

cuisongliu
Copy link
Contributor

No description provided.

@codecov-commenter
Copy link

codecov-commenter commented Nov 18, 2023

Codecov Report

Merging #2537 (c8d2228) into main (6bd1281) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2537   +/-   ##
=======================================
  Coverage   65.86%   65.86%           
=======================================
  Files         133      133           
  Lines       16795    16795           
=======================================
  Hits        11062    11062           
  Misses       5733     5733           

@cuisongliu cuisongliu force-pushed the auto_release_docs_pr branch 6 times, most recently from 8e0c924 to ce3432e Compare November 23, 2023 01:06
@cuisongliu cuisongliu marked this pull request as ready for review November 23, 2023 01:06
sudo env PATH=$PATH just version-up ${{ inputs.version }}
- uses: peter-evans/create-pull-request@v5
with:
title: 'docs: Automated docs Update for ${{ inputs.version }}'
Copy link
Member

Choose a reason for hiding this comment

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

Not only docs but also Cargo.toml.

Copy link
Member

@utam0k utam0k left a comment

Choose a reason for hiding this comment

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

Why don't you use tagpr?
https://github.com/Songmu/tagpr

@cuisongliu
Copy link
Contributor Author

Why don't you use tagpr?
https://github.com/Songmu/tagpr

Looks like this would be a good approach.

@cuisongliu cuisongliu force-pushed the auto_release_docs_pr branch 16 times, most recently from 5bc82d5 to 5b2546b Compare November 26, 2023 09:03
@cuisongliu cuisongliu force-pushed the auto_release_docs_pr branch 7 times, most recently from be4d74e to 32c610a Compare November 26, 2023 14:59
@cuisongliu cuisongliu marked this pull request as ready for review November 26, 2023 15:03
@cuisongliu
Copy link
Contributor Author

  1. update_version_config.yaml action manually modify version number
  2. merge tagpr-xxx branch
  3. using tagpr action auto commit version change
  4. merge tagpr-from-xxxx branch
  5. auto release new version

version:
description: 'Version to release'
required: true
default: '0.3.0'
Copy link
Member

Choose a reason for hiding this comment

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

It is not necessary.

Suggested change
default: '0.3.0'

@@ -0,0 +1,7 @@
[tagpr]
Copy link
Member

Choose a reason for hiding this comment

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

Please add a comment about how we don't need to edit it.

justfile Outdated
Comment on lines 195 to 197
if [[ "{{version}}" == "0.3.0" ]]; then
return
fi
Copy link
Member

Choose a reason for hiding this comment

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

Why do we need it?

Suggested change
if [[ "{{version}}" == "0.3.0" ]]; then
return
fi

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The main thing is that when this PR is submitted, a current version of the PR will be automatically generated. Another way is to change the current default version number to 0.3.1

Copy link
Member

@utam0k utam0k Dec 8, 2023

Choose a reason for hiding this comment

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

It's a good time to release 0.3.1. I'd like to release the new version using the new workflow you created! So can we delete it?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Of course, I've deleted it. When the current PR is merged, it will automatically create a new PR. When the new PR is merged, it can be automatically released.

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Trigger Release Workflow(only when tagged)
uses: actions/github-script@v6
if: "steps.tagpr.outputs.tag != '' && steps.tagpr.outputs.tag != 'v0.3.0'"
Copy link
Member

Choose a reason for hiding this comment

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

Please check format instead of v0.3.0.

Comment on lines 5 to 9
inputs:
version:
description: 'Version to release'
required: true
default: '0.3.0'
Copy link
Member

Choose a reason for hiding this comment

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

Is it difficult to choose major, minor, or patch to take place of a version?

@cuisongliu cuisongliu force-pushed the auto_release_docs_pr branch 2 times, most recently from d770988 to 073d661 Compare November 27, 2023 17:20
@utam0k
Copy link
Member

utam0k commented Dec 7, 2023

@cuisongliu Sorry for the late. May I ask you to rebase this PR from the main branch? We extended the timeout for CI.

@cuisongliu
Copy link
Contributor Author

@cuisongliu Sorry for the late. May I ask you to rebase this PR from the main branch? We extended the timeout for CI.

done

@cuisongliu cuisongliu force-pushed the auto_release_docs_pr branch 2 times, most recently from d53ac07 to fd0a822 Compare December 10, 2023 03:39
Copy link
Member

@utam0k utam0k left a comment

Choose a reason for hiding this comment

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

Looks good except for the conlict

Signed-off-by: cuisongliu <cuisongliu@qq.com>
@utam0k
Copy link
Member

utam0k commented Dec 17, 2023

@cuisongliu Thanks!

@utam0k utam0k merged commit 9b37c2a into youki-dev:main Dec 17, 2023
15 checks passed
@github-actions github-actions bot mentioned this pull request Dec 17, 2023
@cuisongliu cuisongliu deleted the auto_release_docs_pr branch December 17, 2023 11:39
This was referenced Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants