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

Revert "Reintroduce aria-hidden=true asterisk changes" #3465

Conversation

broccolinisoup
Copy link
Member

@broccolinisoup broccolinisoup commented Jun 30, 2023

Reverts #3439

So sorry @adrianababakanian for reverting this again but there are still failing tests at dotcom that relys on having aria-hidden="true" attribute https://github.com/github/github/actions/runs/5418650975/jobs/9850965487?pr=278549

Let us know if you need more support on re-introducing this PR.

@broccolinisoup broccolinisoup requested review from a team and colebemis June 30, 2023 02:54
@changeset-bot
Copy link

changeset-bot bot commented Jun 30, 2023

⚠️ No Changeset found

Latest commit: cc254c5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

size-limit report 📦

Path Size
dist/browser.esm.js 101.82 KB (+0.01% 🔺)
dist/browser.umd.js 102.37 KB (+0.01% 🔺)

@adrianababakanian
Copy link
Contributor

Ah, sorry to have you need to revert again @broccolinisoup ! I thought I caught all of the failing dotcom CI with my canary version installed 😬 Per your understanding, are the four failing tests across the two jobs here a definitive list of what needs to updated in dotcom?

🤞 that third time's a charm 😅

@broccolinisoup
Copy link
Member Author

broccolinisoup commented Jul 3, 2023

@adrianababakanian No worries at all!

Per your understanding, are the four failing tests across the two jobs here a definitive list of what needs to updated in dotcom?

I wouldn't rely on these failures as definitive tests. There might be other jest failures that don't show up on the integration PR.

What I would suggest is installing "0.0.0-20230630025459" version (currently this PR's latest canary) on your dotcom PR that you are "fixing" issues/tests on. In this case I think https://github.com/github/github/pull/278843. After installing the canary version on that PR if there are still failing tests at dotcom you can address them immediately on your PR. Once you see all CI checks are green on your https://github.com/github/github/pull/278843, that means we are good to go 🙂 Is that helpful? Would you need a hand with any of these?

Update: Sorry I was confused and thought this is the re-introduce PR 😬 What I would suggest is installing the canary of your PR that you will re-introduce these changes 😊

@joshblack joshblack added this pull request to the merge queue Jul 3, 2023
Merged via the queue into main with commit c5bd228 Jul 3, 2023
@joshblack joshblack deleted the revert-3439-adrianababakanian/reintroduce-pagination-control-changes branch July 3, 2023 15:44
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.

3 participants