Skip to content

Conversation

@BanaSeba
Copy link
Contributor

Added Github notifications on switch/deploy/release

@BanaSeba BanaSeba requested a review from a team as a code owner April 29, 2025 19:06
@vercel
Copy link

vercel bot commented Apr 29, 2025

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

Name Status Preview Comments Updated (UTC)
admin.ensnode.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 3:48pm
ensnode.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 3:48pm
ensrainbow.io ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 3:48pm

@changeset-bot
Copy link

changeset-bot bot commented Apr 29, 2025

⚠️ No Changeset found

Latest commit: 8007610

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

- name: Slack Notification on Success
if: success()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think if: success() unnecessary?

A default status check of success() is applied unless you include one of these functions.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#status-check-functions

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed

if: success()
uses: rtCamp/action-slack-notify@v2
env:
SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_URL }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would it be beneficial to extract this into a shared action where the default values can be applied? username and icon are static and title/message/color(default good) can be the args. not sure if the secret can be set in the action or whether only the main workflow file has access to secrets. but otherwise that can be provided as a default as well to cut down on the duplication in each workflow we want to notify slack in

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added new action for Slack notification. We can extend it further in the future if needed

redeploy_service ${RAILWAY_ENVIRONMENT_ID} ${ENSRAINBOW_SVC_ID}
- name: Slack Notification on Success
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also happy to remove the name key here, as it'll use the action name by default which is a-ok to me and minimizes our configuration

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed

@shrugs shrugs merged commit f6ed1b7 into main May 8, 2025
8 checks passed
@shrugs shrugs deleted the feat/631-add-slack-notifications-upon-key-ci-actions branch May 8, 2025 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants