-
Notifications
You must be signed in to change notification settings - Fork 426
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
chore(docs): fix dataset delete script #4906
Conversation
- add more logging in delete script - use PR numbers as dataset names instead of github ref
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Component Testing Report Updated Sep 8, 2023 1:13 PM (UTC)
|
No changes to documentation |
.github/workflows/docReport.yml
Outdated
@@ -51,14 +51,14 @@ jobs: | |||
if: ${{ github.event_name == 'pull_request' }} | |||
env: | |||
DOCS_REPORT_TOKEN: ${{ secrets.DOCS_REPORT_DATASET_TOKEN }} | |||
DOCS_REPORT_DATASET: ${{ github.ref_name }} | |||
DOCS_REPORT_DATASET: ${{ github.event.number }} |
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.
should we prefx it so it's easy to identify as a temporary dataset?
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.
sure I can take a look at how to do that
* chore(docs): fix dataset delete script - add more logging in delete script - use PR numbers as dataset names instead of github ref * chore(docs): prefix dataset name with pr * chore(docs): fix turbo token
Description
What to review
Seems like when the PR is closed the ref actually points to the next branch so it ends up deleting the next dataset. It seems like the
github.event.number
should be more consistent. ReferenceNotes for release
N/A