Skip to content

Conversation

@mejo-
Copy link
Member

@mejo- mejo- commented Dec 1, 2025

CI often runs into rate limits when testing against nextcloud.com and we're asked to not use nextcloud.com in tests anyway.

🏁 Checklist

  • Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
  • Sign-off message is added to all commits
  • Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests

@mejo- mejo- self-assigned this Dec 1, 2025
@mejo- mejo- requested a review from max-nextcloud as a code owner December 1, 2025 08:53
@mejo- mejo- added tests If you write them we ♥ you 3. to review labels Dec 1, 2025
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]>
@mejo- mejo- force-pushed the test/no_nextcloud_com branch from f9ff064 to 033860c Compare December 1, 2025 08:56
@mejo-
Copy link
Member Author

mejo- commented Dec 1, 2025

/backport to stable32

@codecov
Copy link

codecov bot commented Dec 1, 2025

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
Copy link
Collaborator

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.

Copy link
Member Author

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 😉

Copy link
Collaborator

@max-nextcloud max-nextcloud left a 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.

@mejo- mejo- merged commit ddf1f5a into main Dec 1, 2025
69 checks passed
@mejo- mejo- deleted the test/no_nextcloud_com branch December 1, 2025 09:30
@mejo-
Copy link
Member Author

mejo- commented Dec 1, 2025

/backport to stable31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review tests If you write them we ♥ you

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants