All Projects → bahmutov → github-post-release

bahmutov / github-post-release

Licence: other
Forms release changelog and posts a note to each referenced issues after semantic release publishes a new module version

Programming Languages

javascript
184084 projects - #8 most used programming language
shell
77523 projects

Projects that are alternatives of or similar to github-post-release

git
🔀 semantic-release plugin to commit release assets to the project's git repository
Stars: ✭ 235 (+1205.56%)
Mutual labels:  changelog, semantic-release
Semantic Release
📦🚀 Fully automated version management and package publishing
Stars: ✭ 14,364 (+79700%)
Mutual labels:  changelog, semantic-release
sv4git
Semantic version and conventional commits for git
Stars: ✭ 33 (+83.33%)
Mutual labels:  changelog, semantic-release
hubkit
Project maintainance tool for GitHub repositories
Stars: ✭ 27 (+50%)
Mutual labels:  changelog
release-changelog-builder-action
A GitHub action that builds your release notes / changelog fast, easy and exactly the way you want.
Stars: ✭ 515 (+2761.11%)
Mutual labels:  changelog
kacl
Keep a Changelog tooling for automating changelog releases
Stars: ✭ 12 (-33.33%)
Mutual labels:  changelog
get-changelog
A CLI tool to easily find changelogs
Stars: ✭ 21 (+16.67%)
Mutual labels:  changelog
gitissue.com
Github Issue Blog Platform,Monkey Write, Monkey Read. Github Issue 博客平台, 黑客写字,画家悦读。
Stars: ✭ 17 (-5.56%)
Mutual labels:  issue
wisdom
🎁 Tool for publishing releases to github and npm
Stars: ✭ 16 (-11.11%)
Mutual labels:  changelog
prepare-commit-msg
Automatically prefix commit messages with the current branch issue number
Stars: ✭ 28 (+55.56%)
Mutual labels:  issue
changelog-enforcer
A simple GitHub action that enforces that a maintained changelog is kept up to date.
Stars: ✭ 32 (+77.78%)
Mutual labels:  changelog
new-issue
A fully customizable Github issues interface. Setup for your repo today!
Stars: ✭ 22 (+22.22%)
Mutual labels:  issue
git-changelog
Categorized change logs from git messages
Stars: ✭ 20 (+11.11%)
Mutual labels:  changelog
issue-blog
基于 GitHub API 的博客工具,尽情享受 GitHub Issue 带来的便利吧。
Stars: ✭ 44 (+144.44%)
Mutual labels:  issue
drone-ci-demo
A Demo to show workflow of Drone CI + GitFlow + Semantic Release + Kubernetes
Stars: ✭ 47 (+161.11%)
Mutual labels:  semantic-release
semantic-release-slack-bot
📦 🚀 A slack bot for semantic-release notifying release statuses
Stars: ✭ 92 (+411.11%)
Mutual labels:  semantic-release
vue-cli-template-library
Template for developing open-source vue.js libraries with Rollup + Jest + Babel + Storybook + TravisCI + SemanticRelease
Stars: ✭ 61 (+238.89%)
Mutual labels:  semantic-release
attribution
Generate changelogs from commit tags and shortlogs
Stars: ✭ 20 (+11.11%)
Mutual labels:  changelog
next-release
Next Release is a release note management platform that automates your release notes in 3 clicks.
Stars: ✭ 18 (+0%)
Mutual labels:  changelog
versioce
Version bumping and changelog generation for your mix project
Stars: ✭ 19 (+5.56%)
Mutual labels:  changelog

github-post-release

Forms release changelog and posts a note to each referenced issues after semantic release publishes a new module version

NPM

Build status semantic-release js-standard-style next-update-travis badge

Problem

When publishing new version of your NPM package, it would be nice to comment on each GitHub issue referenced by the semantic commits, letting the user know that the fix / feature was published.

This module works as a semantic-release generate notes plugin. It both comments on referenced issues and returns the changelog to be posted on GitHub. Each issue will get a comment like this (example)

Typical comment

Install and use

Requires Node version 6 or above.

npm install --save-dev github-post-release

The postinstall script will automatically set this module to be the generateNotes plugin for the release. If you want you can do this manually:

{
  "release": {
    "generateNotes": "github-post-release"
  }
}

Message types

By default, the output message for issues will be "New version has been published to NPM ...". This might not match other scenarios when this plugin can be used. For example if you deploy a website and publish release notes to GitHub, you might like different text that does not mention NPM. There are two built-in message types: "npm", "deploy" and you can pick on to generate by configuring this plugin like this in package.json

{
  "release": {
    "generateNotes": {
      "path": "github-post-release",
      "type": "deploy"
    }
  }
}

Debug

To see more log messages, run this plugin with DEBUG=github-post-release flag. You can even demo the plugin locally (without actual GitHub updates) using npm run demo.

Related

It was inspired by semantic-release-github-notifier, release-notes-generator and uses conventional-changelog to generate changelog text after commenting on issues.

Small print

Author: Gleb Bahmutov <[email protected]> © 2017

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2017 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].