[W-8885816] OFM-NPSP: Automerge major release branches #33
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
spelak-salesforce
added
no QE needed
seanpat09
suggested changes
Feb 12, 2021
- Removed unintended local file changes
|
@jstvz , can you give a codeowner review? I think we still need to wait for the NPSP package version on Spring '21 issue to be resolved before all the feature builds run successfully. |
|
The feature builds should all succeed. MetaCI is pinned to Spring '21 pods until after R2, which happens late tonight. |
|
@SalesforceFoundation/release-engineering-reviewers , can we get a code owner review? Thank you! |
jstvz
approved these changes
Feb 17, 2021
spelak-salesforce
added
🎯 this sprint
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.
Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata
Definition of Done
Refer to Definition of Done to see any additional details for the items below:
Any net new LWC work has JEST test coverage 50% or aboveDefault Sa11y tests pass for all LWC components🔒 Secure both Front-end (LWC) & back-end (Apex) as necessary🔑 Grant users access in Permission Sets (Object, Field, Apex Class) as necessaryPull Request contains draft release notesLabels, help text, and customer facing messages are reviewed by DocsQE story level testing completed