-
-
Notifications
You must be signed in to change notification settings - Fork 400
Spell check #676
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
base: main
Are you sure you want to change the base?
Spell check #676
Conversation
fixes spelling on line 5
🆗 Pre-flight checks passed 😃This pull request has been checked and contains no modified workflow files, spoofing, or invalid commits. It should be safe to Approve and Run the workflows that need maintainer approval. |
Bisaloo
left a comment
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.
Thanks!
|
Hi @froggleston, I believe this is the first PR we received from a fork since the move to the dockerized workflow infrastructure (#650). It seems(??) that PR cannot access the secret to trigger other workflows. Is it something that needs changing in the GitHub organization setting or in the workflow? Or do you think it's something else entirely? |
|
Hey @Bisaloo - hmmm I think the permissions look correct, but I have a feeling it's because we're calling |
|
It's a little weird that |
|
OK I've found the issue. I'll open another workflow PR once I've tested it with another repo. |
fixes spelling on line 5 where "training" was misspelled.