-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
chore: update tag on dev #12599
Closed
Closed
chore: update tag on dev #12599
+760
−1,617
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* ci: add upstream sync * chore: test ci * chore: update ci * ci: add pat env for add upstream remote step * ci: fetch master remote only * chore: update ci * ci: rebase dev onto master branch * chore: test ci * chore: update ci * chore: update ci * ci: add ref * ci: add debug step * ci: update upstream sync * ci: update workflow upstream * chore: add pr dev to test ci * fix: fetch exist -1 * ci: add pr dev branch test ci * chore: update fetch * refactor: facilitate workflow * chore: update ci * chore: add logic when no difference between dev and master branch * chore: update ci * chore: update ci * chore: update ci * chore: update ci * chore: remove extra spaces gh create pr * ci: add wait ci complete * chore: update ci * chore: finish ci
* chore: add CI template * chore: add upstream sync workflow * chore: disable some variants * chore: disable some variants * chore: disable more variants * fix: lint * fix: build * chore: build --------- Co-authored-by: sangjanai <sang@janai>
ci: update upstream sync
…-03-20-23-14 Sync master with upstream release b4930
* ci: update tag * chore: pull request to dev * chore: update ci upstream sync * refactor: remove pull request to dev for testing
Co-authored-by: sangjanai <sang@janai>
…-03-21-03-16 Sync master with upstream release b4932
ci: update tag upstream sync
Co-authored-by: sangjanai <sang@janai>
…-03-24-00-08 Sync master with upstream release b4944
ci: tag commit after sync on dev branch
Co-authored-by: sangjanai <sang@janai>
* chore: use cu12.0 for menlo * chore: typo --------- Co-authored-by: sangjanai <sang@janai>
…-03-25-00-08 Sync master with upstream release b4951
chore: update ci upstream sync
…-03-26-00-08 Sync master with upstream release b4958
…-03-27-00-08 Sync master with upstream release b4966
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a new GitHub Actions workflow to automate syncing the upstream repository and updating the
dev
branch. The workflow is scheduled to run daily at midnight UTC and can also be triggered manually. The most important changes include setting up the workflow, syncing with the latest upstream release, and creating a pull request to update thedev
branch.New GitHub Actions workflow:
.github/workflows/upstream-sync.yml
: Added a new workflow named "Sync Upstream and Update Dev" that runs daily at midnight UTC and can be manually triggered. This workflow performs several steps including checking out the repository, configuring Git, syncing with the latest upstream release, and creating a pull request to update thedev
branch.