Repo Gardening: remove WordPress.com Commit reminder task (#40277)

* Repo Gardening: remove WordPress.com Commit reminder task

Fusion is long dead, long live Fusion.

* Remove other references to Fusion

Co-authored-by: tbradsha <[email protected]>

---------

Co-authored-by: tbradsha <[email protected]>

projects/github-actions/repo-gardening/CHANGELOG.md

@@ -32,7 +32,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Boost: Fix [Boost Feature] labels [#35947]
 - Check description task: Handle empty PR body. [#36446]
 - Repo Gardening: fix workflow for adding [OSS Citizen] label. [#37252]
-- WPCOM Commit Reminder rask: Fix detection of existing reminder comment. [#39042]
+- WPCOM Commit Reminder task: Fix detection of existing reminder comment. [#39042]
 
 ## [5.0.0] - 2024-02-07
 ### Added

projects/github-actions/repo-gardening/README.md

@@ -11,7 +11,6 @@ Here is the current list of tasks handled by this action:
 - Check Description (`checkDescription`): Checks the contents of a PR description, and ensure it matches our recommendations.
 - Add Labels (`addLabels`): Adds labels to PRs that touch specific features.
 - Clean Labels (`cleanLabels`): Removes Status labels once a PR or issue has been closed or merged.
-- WordPress.com Commit Reminder (`wpcomCommitReminder`): Posts a comment on merged PRs to remind Automatticians to commit the matching WordPress.com change.
 - Notify Design (`notifyDesign`): Sends a Slack Notification to the Design team to request feedback, based on labels applied to a PR.
 - Notify Editorial (`notifyEditorial`): Sends a Slack Notification to the Editorial team to request feedback, based on labels applied to a PR.
 - Flag OSS (`flagOss`): flags entries by external contributors, adds an "OSS Citizen" label to the PR, and sends a Slack message.

projects/github-actions/repo-gardening/changelog/rm-repo-gardening-wpcom-commit-reminder

@@ -0,0 +1,4 @@
+Significance: major
+Type: removed
+
+WordPress.com Commit Reminder: remove this task as it is no longer used in the Jetpack monorepo.

projects/github-actions/repo-gardening/src/index.js

@@ -11,7 +11,6 @@ const notifyDesign = require( './tasks/notify-design' );
 const notifyEditorial = require( './tasks/notify-editorial' );
 const replyToCustomersReminder = require( './tasks/reply-to-customers-reminder' );
 const triageIssues = require( './tasks/triage-issues' );
-const wpcomCommitReminder = require( './tasks/wpcom-commit-reminder' );
 const debug = require( './utils/debug' );
 const ifNotClosed = require( './utils/if-not-closed' );
 const ifNotFork = require( './utils/if-not-fork' );
@@ -57,10 +56,6 @@ const automations = [
 		action: [ 'labeled' ],
 		task: ifNotClosed( notifyEditorial ),
 	},
-	{
-		event: 'push',
-		task: wpcomCommitReminder,
-	},
 	{
 		event: 'pull_request_target',
 		action: [ 'opened' ],

projects/plugins/jetpack/changelog/rm-repo-gardening-wpcom-commit-reminder

@@ -0,0 +1,5 @@
+Significance: patch
+Type: other
+Comment: Janitorial: remove references to Fusion.
+
+

projects/plugins/jetpack/extensions/README.md

@@ -301,10 +301,6 @@ In Jetpack the scenario that has been used historically is to create a deprecati
 - You can view the various build commands in `package.json`
 - You can see the build configuration in `webpack.config.extensions.js`
 
-If you need to modify the build process, bear in mind that config files are also
-synced to WordPress.com via Fusion. Consult with a Jetpack crew member to ensure
-you test the new build in both environments.
-
 ### Debugging
 
 Setting these might be useful for debugging with block editor: