We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, both inbrowser.dev and inbrowser.link are updated when the CI job builds HEAD of the main branch.
inbrowser.dev
inbrowser.link
CI
main
We want to keep this behavior for .dev (testion/staging env), but want to stabilize .link and only deploy when a new release is tagged.
.dev
.link
The work is to adjust condition at:
https://github.com/ipfs-shipyard/helia-service-worker-gateway/blob/1bc8d1b7e4b631c837f40b840f598a43a070dba8/.github/workflows/main.yml#L260-L262
The text was updated successfully, but these errors were encountered:
Done in #117
Sorry, something went wrong.
No branches or pull requests
Right now, both
inbrowser.dev
andinbrowser.link
are updated when theCI
job builds HEAD of themain
branch.We want to keep this behavior for
.dev
(testion/staging env), but want to stabilize.link
and only deploy when a new release is tagged.The work is to adjust condition at:
https://github.com/ipfs-shipyard/helia-service-worker-gateway/blob/1bc8d1b7e4b631c837f40b840f598a43a070dba8/.github/workflows/main.yml#L260-L262
The text was updated successfully, but these errors were encountered: