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

Link directly to desired workflow run attempt as opposed to summary for the given commit #142

Conversation

amonshiz
Copy link

@amonshiz amonshiz commented Dec 1, 2022

We have started to add more and more workflows that run on each commit. This makes linking to the summary for the commit less helpful since the investigator for any message must click through multiple levels of links to get to the actual desired information. This change has the “Actions URL” point directly to the currently running workflow attempt instead of the summary.

Resolves #116

@amonshiz
Copy link
Author

@mrrobot47 can this be merged? We have been using this at work for over 2mo and it has dramatically improved our experience.

@sean1588
Copy link

sean1588 commented Feb 3, 2023

@amonshiz this is a fix we needed as well as we are running into the same issue. Since it looks like this PR has not been pending review for a while, I ended up just applying your fix myself and rebuilt it and published my own docker image with your fix since it is something we also need as well. I published it to dockerhub so feel free to use it for yourself, in case you havent already done the same. Thanks for doing this btw.

just update the job to uses: docker://sholung/action-slack-notify:v2.4.1

@bartekpacia
Copy link

+1 to this, I'd be really happy to see this merged!

@wizardone
Copy link

Wondering if anyone is maintaining this anymore? I'll probably end up using the docker image linked above, or maybe just push one myself.

@amonshiz
Copy link
Author

@wizardone we still use this ourselves, though with our own hosted Docker image. I'd guess the one from @sean1588 is identical!

@sean1588
Copy link

@amonshiz - yup I did the same thing. I applied your fix and rebuilt the docker image. y'all feel free to use it.

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