staffbase / autodev-action Goto Github PK
View Code? Open in Web Editor NEWThis GitHub action merges labeled PRs into the dev branch.
License: Apache License 2.0
This GitHub action merges labeled PRs into the dev branch.
License: Apache License 2.0
On bigger repositories, with many dev'ed PRs in parallel, the status comments of this action link all of them as intended.
However this leads to a GitHub annotating each of the PRs with all the other PRs. This is due to GitHub autolinker recognizing the PR-Links and annotating the linked PR with something like "This PR was mentioned in PR".
The Status Comments are nice and give a good feedback of what the action produced, so disabling the comments is not the optimal Solution here.
We should provide a way to reduce the AutoLink spam without giving away the comments nicities.
I was thinking about some kind of templating we can provide for the action. So we can give the Users the ability to Structure the comments themselves.
This is the way for example release-drafter/release-drafter handles dynamic outputs.
So we use some kind of templating Engine (e.g. go-template) and provide the users a documentation of what parameters we compile into the Template. This way they can leave out what they want to leave out, or can even use handmade messages for the Comments โจ ๐จ
debug
Possibility to configure workflows and checks to be successful before merging pull requests to dev-branch
Check the PR workflows/checks and get the status of either a pre-configured list of checks and/or all checks which are required for merge. The second option might be easier to configure at the auto dev action, as it would be just a boolean flag, with the downside that e.g. sonarcube also might prevent the "deving".
Currently pull request with a broken CI pipeline are blocking the auto deving flow as also CI on dev branch is breaking. Often you need then to wait for other PRs to be fixed or "un-deved". By only considering PRs with successful CI pipeline, we could prevent this.
When adding the action to a new repository, it fails when there is no "dev" branch yet.
The action should just create one. Doesn't matter where IMHO, it's force-pushed anyway.
Create a new repo and try to add this action.
n/a
(in a company-internal repository, please contact via Slack if interested)
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.