-
Notifications
You must be signed in to change notification settings - Fork 109
test: Use example.org instead of nextcloud.com for testing links #7998
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
Conversation
CI often runs into rate limits when testing against nextcloud.com and we're asked to not use nextcloud.com in tests anyway. Signed-off-by: Jonas <[email protected]>
f9ff064 to
033860c
Compare
|
/backport to stable32 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was accidently introduced again with 51ac9ad, but we have a different approach in text. JS assets are compiled and pushed to the branches by a CI job after PRs got merged. Signed-off-by: Jonas <[email protected]>
| CYPRESS_INSTALL_BINARY: 0 | ||
| run: | | ||
| npm ci | ||
| npm run build --if-present |
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 think the idea here is to make sure it still builds after the npm audit update. But I guess the same would also happen in the PR created below.
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.
We had this removed in the past as well, see c253378 😉
max-nextcloud
left a comment
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.
example.org also had it's issues once - nextcloud/collectives@858036d
But at least there's no rate limiting.
|
/backport to stable31 |
CI often runs into rate limits when testing against nextcloud.com and we're asked to not use nextcloud.com in tests anyway.
🏁 Checklist
npm run lint/npm run stylelint/composer run cs:check)