forked from woocommerce/woocommerce
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'upstream/trunk' into trunk
- Loading branch information
Showing
11,355 changed files
with
897,630 additions
and
263,273 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,2 @@ | ||
| node_modules | ||
| node_modules | ||
| !.github |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,16 @@ | ||
| * text=auto | ||
|
|
||
| # Force LF In Configuration Files | ||
| *.md text eol=lf | ||
| *.json text eol=lf | ||
| *.yml text eol=lf | ||
|
|
||
| # Force LF In Code Files | ||
| *.php text eol=lf | ||
| *.js text eol=lf | ||
| *.jsx text eol=lf | ||
| *.ts text eol=lf | ||
| *.tsx text eol=lf | ||
| *.css text eol=lf | ||
| *.scss text eol=lf | ||
| *.flf text eol=lf |
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,11 +1,11 @@ | ||
| blank_issues_enabled: true | ||
| contact_links: | ||
| - name: Feature Requests | ||
| url: https://woocommerce.com/feature-requests/woocommerce/ | ||
| about: If you have an idea for a new feature that you wished existed in WooCommerce, take a look at our Feature Requests and vote, or open a new Feature Request yourself! | ||
| - name: 🔒 Security issue | ||
| url: https://hackerone.com/automattic/ | ||
| about: For security reasons, please report all security issues via HackerOne. If the issue is valid, a bug bounty will be paid out to you. Please disclose responsibly and not via GitHub (which allows for exploiting issues in the wild before the patch is released). | ||
| - name: ❓ Support Question | ||
| url: https://woocommerce.com/document/woocommerce-self-service-guide/ | ||
| about: If you have a question please see our docs or use our forums, helpdesk, or Slack community! | ||
| - name: WooCommerce Blocks | ||
| url: https://github.com/woocommerce/woocommerce-gutenberg-products-block | ||
| about: Please report issues for WooCommerce Blocks directly to it's repository. |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| name: 🚧 Code freeze exception request | ||
| description: Request to process a particular pull request as a code freeze exception. | ||
| title: "[CFE]: " | ||
| labels: ["code freeze exception"] | ||
| body: | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| Use this template to request changes to be included in a version of WooCommerce that is past its code freeze date. | ||
| **The request will be reviewed** and accepted or denied: | ||
| * If accepted, please test your changes in against the release branch and merge. | ||
| * If rejected, please change the base against `trunk` and merge it. | ||
| In either case you are responsible for managing the pull request as usual (provide a description, assign reviewers, ensure that CI jobs pass...) | ||
| - type: input | ||
| id: release-number | ||
| attributes: | ||
| label: "Which release does this request apply to?" | ||
| description: "Format: X.Y (Major.Minor)" | ||
| placeholder: "9.2" | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: pr-urls | ||
| attributes: | ||
| label: "Which PR needs to be included? (please do not enter multiple PRs)" | ||
| description: "Pull request URL against the release branch" | ||
| placeholder: | | ||
| https://github.com/woocommerce/woocommerce/pull/1234 | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: why-needed | ||
| attributes: | ||
| label: "Why do these PRs need to break the code freeze?" | ||
| placeholder: "This is a revert of ... which introduced a bug that causes ..." | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| attributes: | ||
| id: consequence-if-not-included | ||
| label: "What is the consequence if this exception does not get included?" | ||
| placeholder: "The ... flow will be broken for ... users" | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: plan-if-defects-discovered | ||
| attributes: | ||
| label: "What is the plan should defects to be discovered in these PRs ahead of final release?" | ||
| placeholder: "Reverting this PR and ... would be enough" | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: how-to-communicate | ||
| attributes: | ||
| label: "How should this change be communicated in the release post on the public developer blog:" | ||
| description: "See the blog at [https://developer.woo.com/blog/](https://developer.woo.com/blog/) cc @woocommerce/developer-advocacy" | ||
| placeholder: "There is no need to add new communication to the already planned one." | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: who-to-ask | ||
| attributes: | ||
| label: "If you’re not available and we have questions about this request, is there another person(s) and/or a team that we can ping?" | ||
| placeholder: "@person or anyone from the ... team" | ||
| validations: | ||
| required: true | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| ## Escape Analysis | ||
| For the sake of expediting this request, the details below can be completed at a later time should you so choose. | ||
| However, the Escape Analysis section is **required** for any accepted Code Freeze Exception. | ||
| In this section: | ||
| * Think about how the bug escaped your team. | ||
| * Write down ideas on how you could prevent this bug – for example, by writing automated tests, creating a new process, or updating documentation. | ||
| * Make a plan with your team to implement the changes proposed above in order to catch the bug earlier next time and add the related tasks to your backlog. | ||
| * Please, add a separate comment that includes the details for the Escape Analysis. Together with this Escape Analysis, please make sure to include an actionable item that covers the gap exposed by this analysis. It could be a GitHub issue, the reference of a new item to discuss in a team meeting, etc. Anything that prevents this analysis from getting lost in P2 will be useful. | ||
| - type: checkboxes | ||
| id: escape-analysis-completed | ||
| attributes: | ||
| label: "Acknowledgement" | ||
| options: | ||
| - label: "I understand that I need to write an incident report (aka Escape Analysis) as a comment on this post. This is required for the request to be accepted." | ||
| required: true | ||
| - label: "I understand that I need to create an issue as a result of the Escape Analysis and reference it in a comment on this post. This can be done at a later time, but it is required for this request to be closed." | ||
| required: true | ||
| - label: "I understand that I will need to merge the PR to the target `release` branch when my request is approved" | ||
| required: true | ||
| - label: "I understand that I will need to merge the followup cherry-picked PR created by the github-actions bot to `trunk` when my request is approved" | ||
| required: true | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| ## Closing checklist | ||
| Please ensure that the following checklist is completed before closing the request: | ||
| - type: checkboxes | ||
| id: closing-checklist | ||
| attributes: | ||
| label: "Closing checklist for Solaris" | ||
| options: | ||
| - label: "Escape analysis completed" | ||
| required: false | ||
| - label: "PR merged to target `release` branch" | ||
| required: false | ||
| - label: "PR cherry-picked to `trunk` (you can find the links in PR comments to verify)" | ||
| required: false | ||
| - label: "Followup issue if any" | ||
| required: false |
Oops, something went wrong.