Closed RickSlc closed 1 year ago
@RickSlc Thanks for this issue. I'll look into it right away.
Did you make sure to give your github secret the scope
of both repo
and workflow
as described here: https://www.ottrproject.org/getting_started.html#6_Set_up_your_GitHub_personal_access_token ?
Yes, my PAT has scope for both repo and workflow. (I'll be back in 2 weeks)
The other thing to check if you know the token has repo and workflow scopes is whether jhudsl-robot has been given write
access. (Just read
or triage
access won't work).
Hi, I am back. The instructions state:
In your repository, go to your Settings > Collaborators & Teams and click on Add people. In the pop up window, search for and add jhudsl-robot.
(select collaborator)
Choose the write option then click Add jhudsl-robot to this repository.
In my case there is not a write option to select when I add a collaborator and I am not seeing where/how to check for write permissions.
Any chance we could zoom for a few minutes? Thanks!
^ This setting was the issue. Going to update this in ottrproject.org
Describe what is not working with the template or is unclear in the documentation
Hi, I am following the Getting Started instructions from https://www.ottrproject.org/getting_started.html#starting-a-new-ottr-course and it appears the options have been updated. There isn't an option Settings/Secrets and Repository Secrets any longer. The options are "Setting/Secrets and variables" with options Actions, Codebases, Dependabots. I have created a key for Dependabots but it doesn't appear to be working.
Please link to the specific course repository you are working on
https://www.ottrproject.org/getting_started.html#starting-a-new-ottr-course
To Reproduce
Expected behavior
Improved/updated description for how to create the GH_PAT key.
Do I need to pass the GH_PAT key somewhere/to someone?
Github actions links
Screenshots
Additional context