Closed brian-rose closed 8 months ago
@brian-rose can you link me to the repository that you are running this on? I've encountered differences in workflow permissions when running on a fork or upstream before (even with the same settings checked as far as I could tell).
https://github.com/brian-rose/fake-cookbook
But I just manually pushed an edit that fixed all the links.
Looking closer at this, I am noticing this line as the cruz ! [remote rejected] main -> main (refusing to allow a GitHub App to create or update workflow
.github/workflows/trigger-replace-links.yamlwithout
workflowspermission
, and this one is concerning because we don't want workflows permission anyway, we don't want to edit the trigger-replace-links.yml
file, but it could try to because the find and replace "find" field of ProjectPythia/cookbook-template
also exists here. I had added an except statement to not look at this file when I was getting a similar issue.
I can see that it is trying to edit the workflow file
From https://github.com/brian-rose/fake-cookbook
* [new branch] gh-pages -> origin/gh-pages
M .github/workflows/trigger-replace-links.yaml
M CITATION.cff
M README.md
M _config.yml
M notebooks/how-to-cite.md
Your branch is up to date with 'origin/main'.
even though .github/workflows/trigger-replace-links.yaml
is set to exclude
Ah, I think there is a typo in this line
It should be .yaml
instead of .yml
I bet that's it!
Should we standardize .yml
vs .yaml
across the project?
Should we standardize
.yml
vs.yaml
across the project?
I've tried to standardize on .yaml
for the GitHub workflow files at least. It's a personal preference of mine. But the rest of the world doesn't always cooperate unfortunately:
environment.yml
at the root of the repository.github/dependabot.yml
So switching everything to .yaml
might break some things. But we can at least be internally consistent within our workflow files.
Following these very terse recommendations: http://yaml.org/faq.html
Sounds like a plan. I can change all the _gallery_info.yml
s if we want, but that seems like a good deal of work.
Sounds like a plan. I can change all the
_gallery_info.yml
s if we want, but that seems like a good deal of work.
Nah, I would leave it the way it is. Then all the yaml files at the root level of the repo have the same extension, which keeps my brain from complaining too much.
Maybe this is user error, but I just tried to run the
trigger-replace-links.yaml
workflow manually from a newly created cookbook. Before running the action, I set the "Ready and write permissions" for workflows following step 6 of this section of the contributors guide.Despite that setting, the workflow seems to be failing due to a permission issue:
@jukent have you seen this before?