Skip to content
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

disable check-release for PRs #6

Merged
merged 1 commit into from
Mar 4, 2023

Conversation

dlqqq
Copy link
Member

@dlqqq dlqqq commented Mar 4, 2023

The check-release workflow can take upwards of 20 minutes because it is doing a dry run of the entire release workflow. While this definitely makes sense for larger projects like JupyterLab, where it can be very difficult to debug CI failures from unknown PRs, it doesn't make sense for a project this size. Manual release via Jupyter Releaser stops broken releases from being published anyways, so intermittently failing CI on main poses no risk to users.

We can re-enable this in the future if necessary.

@dlqqq dlqqq added the enhancement New feature or request label Mar 4, 2023
@dlqqq
Copy link
Member Author

dlqqq commented Mar 4, 2023

Well, there should definitely be a workflow to make the branch at least builds. But that can be added in later.

@dlqqq dlqqq merged commit 3415960 into jupyterlab:main Mar 4, 2023
dbelgrod pushed a commit to dbelgrod/jupyter-ai that referenced this pull request Jun 10, 2024
Marchlak pushed a commit to Marchlak/jupyter-ai that referenced this pull request Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant