peter-evans / commit-comment Goto Github PK
View Code? Open in Web Editor NEWA GitHub action to create a comment for a commit on GitHub
License: MIT License
A GitHub action to create a comment for a commit on GitHub
License: MIT License
Is there an easy way to make this comment on the PR itself, not any of the commits in it?
I have a similar issue as described peter-evans/create-or-update-comment#234 (comment)
Is it possible that this action also accepts body-path
as an input
Im using the PR comment for the TF plan
And then im using the commit comment for the TF apply, this makes the apply even longer than the plan and it would be great if I could also pass it as a file, that was truncated if it goes to large
I am looking for a functionality similar to https://github.com/peter-evans/create-or-update-comment where it allows to update existing comments
The goal is to prevent duplicates when the builds are retried
This is not really an "issue" of this project but today I just noticed that Github officially removed commit comment from the PR timeline.
https://github.blog/changelog/2022-08-04-commit-comments-no-longer-appear-in-the-pull-request-timeline/
timeline display was useful because I have been using this to generate and display the build/deploy info per commit.
While this is not a real issue of this project, I thought I'd share.
Please feel free to close this.
Hi, I recently opened this help request in the comunity section, they told me I should probably have asked here so here I am.
Would you mind reading this and eventually tell me if something like that is possible?
TLDR: i would like to have a variable (output of a command i run in a job) in the body of the comments, is it possible?
Thanks in advance
While omitting the sha
action input just works for regular commits on branches, these comments are not visible when the action is run for pull requests.
The reason is that for pull requests, actions are run on "merge commits", as you explained here and also documented elsewhere.
By using
- uses: peter-evans/commit-comment@v1
with:
body: "I'm sorry Dave, I'm afraid I can't do that."
sha: ${{ github.head_ref }}
... things seem to work for both PRs and regular commits.
If this makes sense, you might want to add a short notice in the README file?
I saw the other issue (#6) about the same thing but didn't get a working solution.
It would be great to have an option to use output files for comments. Something similar to the 'crrate-issue-from-file' action.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.