Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Support resources/ folder being moved on w3c/aria-at for tests import #1207

Draft
wants to merge 2 commits into
base: development
Choose a base branch
from

Conversation

howard-e
Copy link
Contributor

@howard-e howard-e commented Aug 29, 2024

Supporting change for w3c/aria-at#1096.

Note: this should be merged at the time of the next production deployment.

@howard-e howard-e marked this pull request as draft August 29, 2024 14:02
Copy link
Contributor

@stalgiag stalgiag left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@@ -3,7 +3,7 @@
const spawn = require('cross-spawn');

const ariaAtRepo = 'https://github.com/w3c/aria-at.git';
const ariaAtDefaultBranch = 'master';
const ariaAtDefaultBranch = 'move-resources'; // TODO: Revert to 'master' before merging
Copy link
Contributor

Choose a reason for hiding this comment

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

Placing another reminder to change this before merging

Copy link
Contributor

Choose a reason for hiding this comment

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

Or actually I realize now that this is using the aria-at branch that should make this build over here. Perhaps the issues with CI point to a larger issue with the paths?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also wondering that too. Will investigate

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 should be fixed now in 0a54560

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants