contributors-update
A GitHub action to update the contributors file. (by risadams)
release-drafter
Drafts your next release notes as pull requests are merged into master. (by release-drafter)
| contributors-update | release-drafter | |
|---|---|---|
| 1 | 10 | |
| 4 | 3,617 | |
| - | 3.0% | |
| 0.0 | 6.7 | |
| about 2 years ago | 3 months ago | |
| JavaScript | JavaScript | |
| MIT License | ISC License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
contributors-update
Posts with mentions or reviews of contributors-update.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Getting started with Actions
You can view the project here: https://github.com/risadams/contributors-update, And feel free to leave comments or suggestions, everything is MIT license
release-drafter
Posts with mentions or reviews of release-drafter.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-10.
-
Auto Publish/Release - GitHub Actions
For releasing or publishing our code automatically, we will use the action Release Drafter
- Have some Git & GitHub "best practice" questions...
-
Feather’s ultimate guide to development: tips, tricks and best practices
New release drafts are triggered after every commit is pushed to the main staging build. The drafted release (built with release drafter) will contain all the commits added since the previous release and a suggested new version which will follow the Semantic Versioning rules.
-
How to do proper CI/CD with artifact promotion with GitHub Actions.
I am thinking I would have to create a GitHub release manually and then have a workflow listening on the "Release created" event, which would pull the image with the correct commit sha, tag it with the proper version and push it. Or using something like Release Drafter with a PR-based Git flow.
- Use Github Release Tag Name as Version in Cargo.toml?
-
Cookietemple: A cookiecutter based project creation tool
During 2021, we worked hard to improve it furthermore and add new functionality. We just released the latest version of cookietemple. It now includes (beside other templates for example an advanced C++ template or a Java CLI template) a modern python template using poetry, nox (nox-poetry), automatic docs setup as well as many cool and modern GitHub actions, like ReleaseDrafter (https://github.com/release-drafter/release-drafter).
-
Deploying our code at Feather
Every commit pushed to the main branch will trigger a staging build. In addition to this, every commit pushed to the main branch will draft a new release on GitHub with the help of the release drafter.
-
Automating updates from Upstream Source images
We are always actively working on the configuration for Renovate and will continue to fine-tune it. Having pull requests created for every upstream version change will also optimise the generation of automated changelogs (using the excellent Release Drafter GitHub Action we were already using on Lagoon).
-
How FirstPort manage GitHub, using code stored in GitHub
I wanted to provide a way to be able to easily create release notes, to enhance transparency on what we are delivering. I chose to use a tool called Release Drafter in our workflow. I wanted to configure how labels would be used in every repository, and for that, we standardised all labels across all repositories. I use: docs, dependencies, bug, feature, and maintenance.
-
Generate semantic-release with GitHub Actions
release-drafter / release-drafter
What are some alternatives?
When comparing contributors-update and release-drafter you can also consider the following projects:
screenshot-workflow - This workflow will run a local server in a GitHub action, take screenshots using Playwright, upload those screenshots to Imgur, and post them as a comment on an issue or pull request.
semantic-release - :package::rocket: Fully automated version management and package publishing
gobabygo - A nonsense 'Hello World' program with GitHub Action and JavaScript. (which failed)
cookietemple - A collection of best practice cookiecutter templates for all domains and languages with extensive Github support ⛺
samba_source - Samba source code generator.
docs - Packagr is a series of small, language-agnostic, dependency-free, composable tools that let you package and release artifacts and libraries written in any language.