-
Notifications
You must be signed in to change notification settings - Fork 95
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
Action to sync release notes with nebari-docs #1554
Action to sync release notes with nebari-docs #1554
Conversation
* 🔄 Synced local '.github/ISSUE_TEMPLATE/' with remote '.github/ISSUE_TEMPLATE/' MAINT - Sync .github files 🤖 * 🔄 Synced local 'LICENSE' with remote 'LICENSE' MAINT - Sync .github files 🤖 * 🔄 Synced local 'CONTRIBUTING.md' with remote 'CONTRIBUTING.md' MAINT - Sync .github files 🤖 * 🔄 Synced local '.github/ISSUE_TEMPLATE/bug-report.yml' with remote '.github/ISSUE_TEMPLATE/bug-report-nebari.yml' MAINT - Sync .github files 🤖 * 🔄 Synced local '.github/PULL_REQUEST_TEMPLATE.md' with remote '.github/PULL_REQUEST_TEMPLATE_simple.md' MAINT - Sync .github files 🤖 Co-authored-by: nebari-sensei <null>
MAINT - Sync .github files 🤖 Co-authored-by: nebari-sensei <null>
- name: Run Release File Sync ♻️ | ||
uses: BetaHuhn/repo-file-sync-action@v1 | ||
with: | ||
GH_PAT: ${{ secrets.GITHUB_TOKEN }} |
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.
Does secrets.GITHUB_TOKEN
have permission to nebari-dev/nebari-docs
?
If not, do we need a new secret for this?
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.
I'm not sure but we can update this in the future should it fail 👍
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.
@iameskild Looks like it doesn't have access, ref: https://github.com/nebari-dev/nebari/actions/runs/3597037385/jobs/6058376405#step:3:15
I see we use secrets.GH_PAT
in nebari-dev/.github -- @trallard is this secrets.GH_PAT
an org-level secret that we can use here? If not, we can create a new secret with the required scope.
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 for this @pavithraes! Once the merge conflicts are resolved, this can be merged :)
- name: Run Release File Sync ♻️ | ||
uses: BetaHuhn/repo-file-sync-action@v1 | ||
with: | ||
GH_PAT: ${{ secrets.GITHUB_TOKEN }} |
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.
I'm not sure but we can update this in the future should it fail 👍
Reference Issues or PRs
Closes nebari-dev/nebari-docs#160
Supersedes #1502
The same action we're using in
nebari-dev/.github
to sync org-wide files like the license and issue templates.What does this implement/fix?
Put a
x
in the boxes that applyTesting
Any other comments?