Introduce notify-on-force-push workflow

[bmuenzenmeyer]

Description

Adopting the workflow from nodejs/node - https://github.com/rtCamp/action-slack-notify - which will be useful as we add more users with write access to the repo as part of CODEOWNERS work, AND it introduces accountability for existing users.

Should anyone be able to force push at all? I think the answer remains yes, but I want more visibility to it.

Validation

Post-merge, force pushes will send a Slack message to #nodejs-website

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Dec 7, 2024 9:47pm

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no suggestions.

[AugustinMauroy]

Should anyone be able to force push at all?

IMO, no, we have a wait-before-merge policy. In my opinion, merge force push should only be used when it's absolutely necessary to restore/fix something.

[AugustinMauroy]

Also in the rest markdown documents there is no specific mention of #nodejs-website maybe we should do so.

[bmuenzenmeyer]

IMO, no, we have a wait-before-merge policy. In my opinion, merge force push should only be used when it's absolutely necessary to restore/fix something.

Correct - sorry if my language was not clear. I agree there are circumstances that make it necessary / expedient / useful to have force push.

[bmuenzenmeyer]

Also in the rest markdown documents there is no specific mention of #nodejs-website maybe we should do so.

If I am understanding your concern, the webhook secret has the channel baked in to it, that's why you don't see it on the action config at all.

[bmuenzenmeyer]

switching this to DRAFT to make it clear the webhook secret is NOT yet in place

[AugustinMauroy]

If I am understanding your concern, the webhook secret has the channel baked in to it, that's why you don't see it on the action config at all.

Oops, I didn't make myself clear, I was talking about adding a reference to the slack channel in the documentation to explain that part of the discussion takes place there. For example on the readme or contributing.md

[bmuenzenmeyer]

SLACK_WEBHOOK created by openjs admins, I've added it as a repo secret

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 100	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 100	🟢 100	🟢 96	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 96	🟢 92	🔗

[github-actions]

Unit Test Coverage Report

Lines	Statements	Branches	Functions
	90.79% (631/695)	72.44% (184/254)	94.53% (121/128)

Unit Test Report

Tests	Skipped	Failures	Errors	Time
143	0 💤	0 ❌	0 🔥	5.422s ⏱️

[ovflowd]

Thanks for the effort here, @bmuenzenmeyer <3