release-automation
Here are 257 public repositories matching this topic...
-
Updated
Dec 23, 2020 - JavaScript
-
Updated
Dec 5, 2020 - Groovy
-
Updated
Dec 28, 2020 - JavaScript
-
Updated
Dec 26, 2020 - Python
-
Updated
Nov 22, 2020 - JavaScript
-
Updated
Dec 11, 2020 - Groovy
We have a workflow where we want do generate the release notes only from pull requests and mention the pull request author. I have found no way to do this yet...
-
Updated
Dec 14, 2019 - JavaScript
-
Updated
Nov 13, 2020 - JavaScript
-
Updated
Nov 26, 2020 - Groovy
I am not sure if this belongs here, but I am having an issue when using this Github Action.
This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120
and the content is:
Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl
0%| | 0.00/30.5k [00:00<?, ?B/s]
100%|
-
Updated
Dec 28, 2020 - JavaScript
-
Updated
Dec 6, 2020 - Scala
-
Updated
Nov 28, 2018 - Go
-
Updated
Dec 4, 2020 - Go
-
Updated
Dec 22, 2020 - C#
When "org.shipkit.javadoc" plugin is applied, then release notes should contain a link (as a badge) to the published Javadoc.
By default, the link should point to the specified directory ("javadoc.repositoryDirectory") and branch "javadoc.repositoryBranch" (see ShipkitConfiguration.java for more configuration options).
There should be also a possibility to point to some class, e.g. for Mock
-
Updated
Nov 20, 2020 - Kotlin
-
Updated
Apr 2, 2020 - Shell
-
Updated
Dec 24, 2020 - Java
-
Updated
Apr 23, 2019 - JavaScript
-
Updated
Oct 7, 2020 - PowerShell
-
Updated
Dec 22, 2020
Deployment history list items > Tooltips do not show on all items (Should be shown for all items on hover)
-
Updated
Oct 22, 2018
-
Updated
Dec 24, 2020 - TypeScript
Improve this page
Add a description, image, and links to the release-automation topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the release-automation topic, visit your repo's landing page and select "manage topics."


Most of the documentation has been rewritten recently. The content minimum content we need is there but there is a lot that can be done to improve it.
If you'd like to contribute to the semantic-release project, helping with the following would be much appreciated: