-
Notifications
You must be signed in to change notification settings - Fork 131
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
📝 update "how to cut a release" doc #461
Conversation
✅ Deploy Preview for actualbudget-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
__Login to the Microsoft Partner Center:__ | ||
**Login to the Microsoft Partner Center:** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These formatting changes are coming from prettier. Would be nice to add a pre-commit hook to this repo that would run prettier on the staged files. 💡
|
||
After the release is out on `actual-server` - remember to deploy it and do a quick smoke test to verify things still work as expected. If they do: continue with sending an announcement on Discord and Twitter. | ||
|
||
:tada: |
Check failure
Code scanning / check-spelling
Unrecognized Spelling Error documentation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Update for https://github.com/actualbudget/docs/actions/runs/11166959821/attempts/1 Accepted in #461 (comment) Signed-off-by: check-spelling-bot <check-spelling-bot@users.noreply.github.com> on-behalf-of: @check-spelling <check-spelling-bot@check-spelling.dev>
⌛ check-spelling changes appliedAs configured, the commit pushed by @check-spelling-bot to GitHub doesn't trigger GitHub workflows due to a limitation of the @github-actions system. Users with the Admin role can address this for future interactions 🪄Create a deploy key and secret(
set -e
brand=check-spelling; repo='actualbudget/docs'; SECRET_NAME=CHECK_SPELLING
cd "$(mktemp -d)"
ssh-keygen -f "./$brand" -q -N "" -C "$brand key for $repo"
gh repo deploy-key add "./$brand.pub" -R "$repo" -w -t "$brand-talk-to-bot"
gh secret -R "$repo" set "$SECRET_NAME" < "./$brand"
) Configure update job in workflow to use secretIf the name: Update PR
...
steps:
...
- name: apply spelling updates
uses: ${action_ref:-check-spelling/check-spelling@...}
with:
checkout: true
+ ssh_key: "${{ secrets.CHECK_SPELLING }}" To trigger another validation round and hopefully a ✅, please add a blank line, e.g. to .github/actions/spelling/expect.txt and commit the change. |
No description provided.