Fixes #1327 - Adds OpenJS Github Continuity Policy #1348
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
Fixed linter complaints. Signed-off-by: Benjamin Sternthal <ben@devpatch.com>
ljharb
reviewed
Jul 29, 2024
erickzhao
reviewed
Jul 29, 2024
|
Given that option 3 is to opt-out I can't see a reason not to include existing projects. |
UlisesGascon
approved these changes
Jul 31, 2024
Co-authored-by: Erick Zhao <erick@hotmail.ca> Co-authored-by: Jordan Harband <ljharb@gmail.com> Signed-off-by: Benjamin Sternthal <ben@devpatch.com>
Removed hard line breaks per feedback. Signed-off-by: Benjamin Sternthal <ben@devpatch.com>
timmywil
approved these changes
Aug 2, 2024
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.
This PR adds the Github Continuity Policy discussed in #1327. Note there was discussion around the applicability of the policy to existing projects with at least one person suggesting that the policy only be enforced for new projects.
I would recommend making the policy retro-active and applicable to all projects, primarily for the following two reasons: