Skip to content
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): compare PRs against next branch instead of current #4904

Merged
merged 2 commits into from Sep 7, 2023

Conversation

binoy14
Copy link
Contributor

@binoy14 binoy14 commented Sep 7, 2023

Description

  • fixes token mismatch when deleting dataset
  • better message when no changes to documentation coverage

What to review

The actions conditionals are valid

Notes for release

N/A

@vercel
Copy link

vercel bot commented Sep 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
performance-studio ✅ Ready (Inspect) Visit Preview Sep 7, 2023 7:52pm
test-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 7, 2023 7:52pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
studio-workshop ⬜️ Ignored (Inspect) Visit Preview Sep 7, 2023 7:52pm

- name: Create Docs Report on current
if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/current' }}
- name: Create Docs Report on current or next
if: ${{ github.event_name == 'push' && (github.ref == 'refs/heads/current' || github.ref == 'refs/heads/next') }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if the event_name is still push when a PR is merged. Does anyone know?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fair to assume so, esp. since there doesn't seem to be a merge event.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be trial and error. I will merge and check

@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

Component Testing Report Updated Sep 7, 2023 7:56 PM (UTC)

File Status Duration Passed Skipped Failed
formBuilder/ArrayInput.spec.tsx ✅ Passed (Inspect) 13s 3 0 0
formBuilder/inputs/PortableText/Annotations.spec.tsx ✅ Passed (Inspect) 8s 3 0 0
formBuilder/inputs/PortableText/Decorators.spec.tsx ✅ Passed (Inspect) 9s 6 0 0
formBuilder/inputs/PortableText/Input.spec.tsx ✅ Passed (Inspect) 12s 9 0 0
formBuilder/inputs/PortableText/ObjectBlock.spec.tsx ✅ Passed (Inspect) 44s 18 0 0
formBuilder/inputs/PortableText/Styles.spec.tsx ✅ Passed (Inspect) 10s 6 0 0
formBuilder/inputs/PortableText/Toolbar.spec.tsx ✅ Passed (Inspect) 5s 3 0 0

@github-actions
Copy link
Contributor

github-actions bot commented Sep 7, 2023

No changes to documentation

- fixes token mismatch when deleting dataset
- better message when no changes to documentation
Copy link
Member

@bjoerge bjoerge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

- name: Create Docs Report on current
if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/current' }}
- name: Create Docs Report on current or next
if: ${{ github.event_name == 'push' && (github.ref == 'refs/heads/current' || github.ref == 'refs/heads/next') }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fair to assume so, esp. since there doesn't seem to be a merge event.

@binoy14
Copy link
Contributor Author

binoy14 commented Sep 7, 2023

oh just realized the next branch is not in the allowed list for the workflow to run. Will add it

@binoy14 binoy14 added this pull request to the merge queue Sep 7, 2023
Merged via the queue into next with commit c27ee3e Sep 7, 2023
17 checks passed
@binoy14 binoy14 deleted the feature/sdx-727 branch September 7, 2023 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants