You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you may know, I've added actions to automatically ingest and merge HPC-BP webinar events and the curated content summary article (updated with each new webinar after the fact) generated on the ideas-productivity.org site. The step that merges the pull request requires special permissions and I think may require the person who runs it to generate a personal access token and store it as a secret in the repository.
I need someone to help me test that. It will involve invoking the action, hopefully just once or twice, and perhaps generating a personal access token and storing it as a secret in the repo. We'll do this in conjunction with publishing/updating these articles for regular production purposes, so it will need to be done timely, but it shouldn't require too much time or effort.
One opportunity will come in the first week or two of June, and the next towards the end of June.
Thanks
The text was updated successfully, but these errors were encountered:
As you may know, I've added actions to automatically ingest and merge HPC-BP webinar events and the curated content summary article (updated with each new webinar after the fact) generated on the ideas-productivity.org site. The step that merges the pull request requires special permissions and I think may require the person who runs it to generate a personal access token and store it as a secret in the repository.
I need someone to help me test that. It will involve invoking the action, hopefully just once or twice, and perhaps generating a personal access token and storing it as a secret in the repo. We'll do this in conjunction with publishing/updating these articles for regular production purposes, so it will need to be done timely, but it shouldn't require too much time or effort.
One opportunity will come in the first week or two of June, and the next towards the end of June.
Thanks
The text was updated successfully, but these errors were encountered: