Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Slack Webhook (secret) for nodejs-website #38

Open
bmuenzenmeyer opened this issue Jan 24, 2025 · 1 comment
Open

Create Slack Webhook (secret) for nodejs-website #38

bmuenzenmeyer opened this issue Jan 24, 2025 · 1 comment
Assignees
Labels

Comments

@bmuenzenmeyer
Copy link

Contact Details

[email protected]

Description

As part of improving security and awareness within a core repo of the Node.js project, I'd like to introduce a Slack notification mechanism to the #nodejs-website channel whenever a git push --force occurs to the main branch. This is an extreme action with a lot of responsibility, that is sometimes warranted. We even let people do this on the main repo, FWIW.

I am tracking this work within nodejs/nodejs.org#7322 - in fact, it's done, except for a Slack Webhook required to post to Slack when the workflow conditions are met. As you can see in the pull request, this pattern is directly employed within the main nodejs channel and repo too.

What I think would be required (hard to know for certain the steps without the access), according to the action's documentation, is to use the incoming webhooks slack app to generate the webhook. As far as I know, the webhook -should- be associated with a channel at the time of creation, which I request as #nodejs-website

Warning

(A webhook is a secret that automatically gives anyone with it the power to post to the channel. Whoever makes this, please email it to me directly or use a Slack DM

I've approached this subject within the #foundation slack channel, talking to @joesepi, @bensternthal and @Trott and @GeoffreyBooth, eventually landing here as a good way to track the request officially and get it prioritized.


If successful, nodejs/release-cloudflare-worker#256 would also like this functionality. If they need to be separate requests, that's fine too. The main goal is visibility to such powerful administrative actions.

Project

nodejs

How urgent is this request?

Request / No Problem But Require Assistance or Support

@bensternthal
Copy link
Contributor

Webhook sent to Brian. We will keep this open until @bmuenzenmeyer confirms it is working correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

2 participants