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

Add option to auto deploy to docs-latest #8037

Merged
merged 24 commits into from
Nov 13, 2024
Merged

Add option to auto deploy to docs-latest #8037

merged 24 commits into from
Nov 13, 2024

Conversation

jprochazk
Copy link
Member

@jprochazk jprochazk commented Nov 7, 2024

What

  • Add PR check which ensures that the squashed merge commit can be cherry-picked into docs-latest
  • Add a job which cherry-picks squashed merge commits from main to docs-latest
  • Both run only runs when deploy docs label is present

I believe after this PR, we've got a much better documentation authoring experience, without too much additional complexity. All of these jobs can be easily ripped out if we decide to do something else.

Checklist

  • I have read and agree to Contributor Guide and the Code of Conduct
  • I've included a screenshot or gif (if applicable)
  • I have tested the web demo (if applicable):
  • The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
  • If applicable, add a new check to the release checklist!
  • If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

To run all checks from main, comment on the PR with @rerun-bot full-check.

To deploy documentation changes immediately after merging this PR, add the deploy docs label.

@jprochazk jprochazk added 🧑‍💻 dev experience developer experience (excluding CI) exclude from changelog PRs with this won't show up in CHANGELOG.md 🚢 CI labels Nov 7, 2024
@jprochazk jprochazk added the deploy docs Once this PR is merged to main, the resulting commit will be cherry-picked to docs-latest label Nov 7, 2024
@jprochazk
Copy link
Member Author

jprochazk commented Nov 8, 2024

I decided to do the rest of my testing in a separate repo, so that I could actually push commits to main: https://github.com/jprochazk/ci-playground/actions/workflows/cherry-pick.yml

@jprochazk jprochazk marked this pull request as ready for review November 8, 2024 11:49
Copy link

github-actions bot commented Nov 8, 2024

Your changes can be cherry-picked to docs-latest and will be deployed
immediately after merging.

@jprochazk
Copy link
Member Author

Check links seems to be failing on main

@teh-cmc teh-cmc self-requested a review November 13, 2024 08:01
@jprochazk jprochazk merged commit bb56075 into main Nov 13, 2024
34 checks passed
@jprochazk jprochazk deleted the jan/auto-cherry-pick branch November 13, 2024 11:12
rerun-bot pushed a commit that referenced this pull request Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy docs Once this PR is merged to main, the resulting commit will be cherry-picked to docs-latest 🧑‍💻 dev experience developer experience (excluding CI) exclude from changelog PRs with this won't show up in CHANGELOG.md 🚢 CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants