👷 Remove useless CI stage (HEAD) #720
Merged
Conversation
This file contains 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
HEAD was initially responsible to check for future regressions introduced by libraries. Now that dependabot bumps libraries for us, this is needed anymore. The only thing we will lose if that it was also checking that fast-check will still work with latest revisions of node. Actually it should not be a real issue...
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit b2cd465:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why is this PR for?
HEAD was initially responsible to check for future regressions introduced by libraries.
Now that dependabot bumps libraries for us, this is needed anymore.
The only thing we will lose if that it was also checking that fast-check will still work with latest revisions of node. Actually it should not be a real issue...
In a nutshell
❌ New feature
❌ Fix an issue
❌ Documentation improvement
✔️ Other: ci
(✔️: yes, ❌: no)
Potential impacts
None