-
Notifications
You must be signed in to change notification settings - Fork 153
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
🔖 (23.10.0) #268
🔖 (23.10.0) #268
Conversation
MatissJanis
commented
Oct 2, 2023
•
edited
Loading
edited
- web: 🔖 (23.10.0) actual#1757
- server: 🔖 (23.10.0) actual-server#269
- docs: 🔖 (23.10.0) #268
✅ Deploy Preview for actualbudget-website ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
check-spelling found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.
This comment has been minimized.
This comment has been minimized.
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.
all the flagged spelling errors are fine, unless you feel like you need to change "gitbuh" to "github" on #1692.
This comment has been minimized.
This comment has been minimized.
@check-spelling-bot apply updates. |
@check-spelling-bot: Could not perform request. The referenced report comment is hidden (outdated). This probably means the referenced report has been obsoleted by a more recent push & review. Did you mean to apply the most recent report (#268 (comment))? See log for details. |
This comment has been minimized.
This comment has been minimized.
Update for https://github.com/actualbudget/docs/actions/runs/6392905235/attempts/1 Accepted in #268 (comment) Signed-off-by: check-spelling-bot <[email protected]> on-behalf-of: @check-spelling <[email protected]>
⌛ 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. |