mozilla-mobile / mozilla-mobile/testops-dashboard

Feat: Slack Payload Tweaks

Open
#199 0 comments 0 reactions 1 assignee View on GitHub

@AaronMT is already working on this.

Since Sep 15, 2025.

enhancement
Dominant language
Python
Stars
7
Forks
7
Avg merge
24m
Merged PRs (30d)
2

Description

Block-kit Builder: link
Current payload example:

Image
{
    "attachments": [
        {
            "color": "${{ env.JOB_STATUS_COLOR }}",
            "blocks": [
                {
                    "type": "header",
                    "text": {
                        "type": "plain_text",
                        "text": ":looker: Looker Github Action :github: - ${{ env.WORKFLOW_NAME }}",
                        "emoji": true
                    }
                },
                {
                    "type": "divider"
                },
                {
                    "type": "section",
                    "text": {
                        "type": "mrkdwn",
                        "text": "Status: ${{ env.JOB_STATUS }}\n Logs: <${{ env.JOB_LOG_URL }}|Build Logs>\n Branch: ${{ env.BRANCH }}"
                    }
                },
                {
                    "type": "divider"
                },
                {
                    "type": "context",
                    "elements": [
                        {
                            "type": "mrkdwn",
                            "text": ":testops-notify: created by <https://mozilla-hub.atlassian.net/wiki/spaces/MTE/overview#Test-Operations|Mobile Test Engineering>"
                        }
                    ]
                }
            ]
        }
    ]
}

@rpappalax's initial suggestion:

Image

PROD comes from the workflow names, so they can be renamed no problem

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.