Add prefix dev to cloud services #2697
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for conda-forge-previews ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
afshin
force-pushed
the
add-prefix-dev-to-cloud-services
branch
from
36a87fa to
d1f1b6e
Compare
Member
Author
wolfv
approved these changes
Dec 19, 2025
afshin
force-pushed
the
add-prefix-dev-to-cloud-services
branch
from
d1f1b6e to
9b57836
Compare
Member
|
When is this useful in the context of conda-forge? AFAIK we don't use any of the APIs mentioned in the status page in conda-forge. |
Member
Author
|
Prefix.dev hosts a conda-forge channel and it's that uptime status that I was proposing for the status page. I'm not a maintainer and I am happy to defer to you folks when it comes to decision-making. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the monitor status for
repo.prefix.devto the cloud services section of the status page. I am not 100% confident thatrepo.prefix.devis the correct monitor to query, if someone can authoritatively comment on this I would appreciate it!The monitoring API they use is UptimeRobot and the format most of the other services we query use is StatusPage, so we have a small section of logic that normalizes the status of these API responses. I updated this snippet of logic to support UptimeRobot monitor responses.
PR Checklist:
docs/orcommunity/, you have added it to the sidebar in the corresponding_sidebar.jsonfile