-
Notifications
You must be signed in to change notification settings - Fork 5
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
feat: add scheduled:standup-reminder task #24
Conversation
40fced1
to
d4b9856
Compare
I'm thinking about reorganizing this and the corresponding artsy/README PR: artsy/README#367
That should give us the ability to format richer input here and rely less on downstream clients to reformat output for Slack. Thoughts? |
386d615
to
d01df00
Compare
Experimenting with a GitHub Action + Artsy CLI approach. - artsy/README#367 - artsy/cli#24
Experimenting with a GitHub Action + Artsy CLI approach. - artsy/README#367 - artsy/cli#24
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love this direction and thinking, very cool stuff @dblandin!! 🙌 ❤️ 🏆
- Extract OpsGenie code into utility class - Fix custom TypeScript types with `ts-node/register/transpile-only` mocha option
**Example** ``` $ artsy on-call:who Devon Blandin Jon Allured ```
bcc34a0
to
c388334
Compare
This is the first of a few tasks that I plan to migrate over to the CLI to simplify some of our culture ops automation. The idea is to invoke this task on a similar schedule (every Monday morning at 9am ET) via GitHub Actions (probably in the artsy/README repo). https://github.com/artsy/peril-settings/blob/master/tasks/standupReminder.ts
Outputs a Slack-formatted message including open RFC issues in the Artsy GitHub org. **Example** ``` $ artsy scheduled:rfcs {"text":"There is one open RFC:","attachments":[{"fallback":"Open RFCs","color":"#36a64f","author_name":"jonallured","author_link":"https://github.com/jonallured","title":"RFC: Slight Rebranding for Artsy Engineering","title_link":"https://github.com/artsy/README/issues/364"}],"unfurl_links":false} ```
c388334
to
bc4dd5d
Compare
🚀 PR was released in |
🚀 PR was released in |
🚀 PR was released in |
5 similar comments
🚀 PR was released in |
🚀 PR was released in |
🚀 PR was released in |
🚀 PR was released in |
🚀 PR was released in |
This workflow was pinned to the alpha NPM tag while artsy/cli#24 was still open. We can use the stable channel now.
This workflow was pinned to the alpha NPM tag while artsy/cli#24 was still open. We can use the stable channel now.
This is the first of a few tasks that I plan to migrate over to the CLI to simplify some of our culture ops automation.
The idea is to invoke this task on a similar schedule (every Monday morning at 9am ET) via GitHub Actions (probably in the artsy/README repo).
https://github.com/artsy/peril-settings/blob/master/tasks/standupReminder.ts
#FF #FutureFriday
Example
The output here is intended for a Slack destination. The output includes formatted Slack @-mentions and links.