Support more filters in slack notification

[cychiuae]

Original in #16, we supported filtering by a check conclusion when sending slack notification.

We want to enhance this filtering such that it also supports filter the job/check/action we want to report to slack.

To be think / research about:

• Slack command syntax
  • We can follow the previous github slack command
    • Reference: https://github.com/integrations/slack?tab=readme-ov-file#customize-your-notifications
• Is it backward compatible if we modify the slack command

[cychiuae]

I imagine something like

• /gha subscribe oursky/github-actions-manager branches:[branch_names,comma_separated/*]:[job_statuses,comma_separated]
  • e.g. /gha subscribe oursky/github-actions-manager branches:branch_1,branch_2:failure,timed_out
• /gha subscribe oursky/github-actions-manager workflows:[workflow_names,comma_separated/*]:[job_statuses,comma_separated]
  • e.g. /gha subscribe oursky/github-actions-manager workflows:workflow1,workflow2:failure,timed_out
• /gha subscribe oursky/github-actions-manager workflows:[worflow_names,comma_separated/*]:[job_statuses,comma_separated] branches:[branch_names,comma_separated/*]:[job_statuses,comma_separated]
• /gha subscribe oursky/github-actions-manager -> /gha subscribe oursky/github-actions-manager all

/gha subscribe oursky/github-actions-manager -> means all jobs, all statuses
/gha subscribe oursky/github-actions-manager feature:feature_names[:statuses] feature_2:feature_2_names[:statuses]

[cychiuae]

1. Setup own repo for running github action tasks
2. Follow readme to setup the development enviroment
3. Update readme if necessary
4. Think about how to we store the configurations
5. Implement fs kv storage
6. Runtime migration on old config structure to new config structure
7. Implement the above ^^^^^^

[Kuixz]

• Setup own repo for running github action tasks
• Follow readme to setup the development enviroment
• Update readme if necessary
• Think about how to we store the configurations
• Implement fs kv storage
• Runtime migration on old config structure to new config structure
• Implement the above ^^^^^^

[Kuixz]

• /gha subscribe owner/repo branches:[branch_names,comma_separated/*]:[job_statuses,comma_separated]

• /gha subscribe owner/repo branches:branch_1,branch_2:failure,timed_out

• /gha subscribe owner/repo workflows:[workflow_names,comma_separated/*]:[job_statuses,comma_separated]

• /gha subscribe owner/repo workflows:workflow1,workflow2:failure,timed_out

• /gha subscribe owner/repo workflows:[worflow_names,comma_separated/*]:[job_statuses,comma_separated] branches:[branch_names,comma_separated/*]:[job_statuses,comma_separated]

• /gha subscribe owner/repo -> /gha subscribe owner/repo all