gh-project-context

Build project context and correct Project version in any language version before release.

This action is build a Project context depends on GitHub event to make decision in further step, e.g: do build, do test, do analysis, do tag, do release based on your workflow model.

It also verifies and corrects automatically Project version in metadata file in release pull request or tag:

• NodeJS: package.json
• Java: Gradle with gradle.properties
• Python: Poetry with pyproject.toml or version.py
• Plain text: VERSION.txt
• Or any version metadata file if you know some magical regex skill

Usage

Trigger precondition

The usual example

on:
create:
branches: [ 'release/**' ] ## To create a release PRpush:
branches: ## On main branch, hotfix branch and/or all release branches (optional) 
- main
- hotfix/**
- release/**tags: [ 'v*' ] ## Release tag versionpaths-ignore:
- '.github/ISSUE_TEMPLATE/**'
- '.github/*.yml'
- 'LICENSE'pull_request:
types: [ opened, synchronize, reopened, closed ]branches:
- main
- hotfix/**paths-ignore:
- '.github/ISSUE_TEMPLATE/**'
- '.github/*.yml'
- 'LICENSE'

More detailed at GitHub docs

Integrate the action in your workflow

You can use this action in 2 ways:

1. Add it as first job in your workflow

jobs:
context:
runs-on: ubuntu-latestoutputs:
branch: ${{ steps.context.outputs.branch }}shouldBuild: ${{ steps.context.outputs.decision_build }}shouldPublish: ${{ steps.context.outputs.decision_publish }}isRelease: ${{ steps.context.outputs.isTag && steps.context.outputs.isRelease }}version: ${{ steps.context.outputs.version }}commitId: ${{ steps.context.outputs.commitShortId }}semanticVersion: ${{ steps.semantic.outputs.semanticVersion }}steps:
- uses: actions/checkout@v3
- name: Project contextid: contextuses: zero88/gh-project-context@v2build:
runs-on: ubuntu-latestneeds: contextif: needs.context.outputs.shouldBuild == 'true' # condition to build

2. Add it as step in your job

jobs:
matrix:
runs-on: ubuntu-lateststeps:
- uses: actions/checkout@v2
- name: Project contextuses: zero88/gh-project-context@v1id: project_context
- name: Build projectif: steps.project_context.outputs.decision_build == 'true' # condition to buildshell: bashruns: | npm ci npm run build - name: Build projectif: steps.project_context.outputs.decision_publish == 'true' # condition to publishshell: bashruns: | npm publish

Action output

Run zero88/gh-project-context@v1.2
Loading...
[CI::Process] Evaluate context on main
Searching version in file...
Current Version: 0.0.3
Project context
Version context
{
"branch": "main",
"current": "0.0.3",
"version": "0.0.3"
}
CI context
{
"isPushed": false
}
CI decision
{
"build": true,
"publish": true
}
Action Output
{
"branch": "main",
"onDefaultBranch": true,
"isBranch": true,
"isPR": false,
"isTag": false,
"isSchedule": false,
"isDispatch": false,
"isAfterMergedReleasePR": false,
"isClosed": false,
"isMerged": false,
"isOpened": false,
"isRelease": false,
"commitId": "c1c69ba9f41eeffaf260b7a6174fc37493c8fb42",
"commitMsg": "chore: bump to next version",
"commitShortId": "c1c69ba",
"ci_isPushed": false,
"decision_build": true,
"decision_publish": true,
"version": "0.0.3",
"versions_branch": "main",
"versions_current": "0.0.3"
}

Input and Output

Input

Name	Description	Required	Default value
defaultBranch	Project default branch	false	main
tagPrefix	Tag Prefix	false	v
releaseBranchPrefix	Git Release Branch Prefix	false	release/
hotfixPrefix	Git Hotfix Prefix	false	hotfix/
mergedReleaseMsgRegex	Merged release message regex	false	^Merge pull request #[0-9]+ from .+/release/.+$
patterns	The patterns to search/replace a version. E.g: <glob_pattern_with_ext>::<regex_group>::<version_regex>	false	See below
shaLength	Create output short commit id within length	false	7
allowCommit	CI: Allow git commit to fix version if not match	false	true
allowTag	CI: Allow git tag if merged release branch	false	true
userName	CI: Username to commit	false	ci-bot
userEmail	CI: User email to commit	false	actions@github.com
mustSign	CI: Required GPG sign when git commit/tag	false	false
prefixCiMsg	CI: Prefix bot message	false	<ci-auto-commit>
correctVerMsg	CI: Correct version message template	false	Correct version
releaseVerMsg	CI: Release version message template	false	Release version
nextVerMsg	CI: Next version message template	false	Next version
nextVerMode	CI: Next version mode to choose for upgrading version after merged release PR. One of: MAJOR,MINOR,PATCH,NONE	false	NONE
token	CI: GitHub token to create a new Release Pull Request	false	``
dry	CI: Dry run. If true, action will run without do modify files or git push or git tag	false	false
changelog	Enable generate CHANGELOG	false	false
changelogImage	CHANGELOG docker image tag: https://github.com/github-changelog-generator/docker-github-changelog-generator	false	githubchangeloggenerator/github-changelog-generator:1.16.2
changelogConfigFile	CHANGELOG config file: https://github.com/github-changelog-generator/github-changelog-generator#params-file	false	.github_changelog_generator
changelogToken	CHANGELOG token to query GitHub API: https://github.com/github-changelog-generator/github-changelog-generator#github-token	false
changelogMsg	CI: Changelog generator commit message template	false	Generated CHANGELOG

Default Pattern Input

pyproject.toml::(version\s?=\s?)(")([^"]+)(")::2
package?(-lock).json::("version"\s?:\s?)(")([^"]+)(")::2
@(gradle|maven|pom|project).properties::(version\s?=\s?)(.+)::1
@(application|version).yml::(version:\s)(.+)::1
@(VERSION|version)?(.txt)::.+::0

Output

Project context based on current GitHub event

Name	Description
branch	Current branch name or tag name
onDefaultBranch	Check whether current event is on default branch or not
onRelease	Check whether current event is on release or not, that means isRelease && isTag
isBranch	Check whether current event is on branch or not
isPR	Check whether current event is on pull request or not
isTag	Check whether current event is on ref tag
isSchedule	Check whether current event is by schedule or not
isDispatch	Check whether current event is by manual or dispatch from another workflow or event from repository
isRelease	Check whether current event is release event on regardless of branch, pull-request or tag
isHotfix	Check whether current event is hotfix event on regardless of branch, pull-request or tag
isAfterMergedReleasePR	Check whether current event is a merged commit after merged release pull request into default branch or not
isMerged	Check whether current event is merged PR
isClosed	Check whether current event is close PR but not merged into target branch
isOpened	Check whether current event is open PR or create branch
prBaseBranch	Base branch in pull request
commitMsg	The latest commit message
commitId	The latest commit id
commitShortId	The latest short commit id
version	Current tag version or release version
ci_mustFixVersion	CI: Need to fix version to match with release name
ci_needPullRequest	CI: Need to open new pull request for release or merge hotfix into default branch
ci_needTag	CI: Need to tag new version if release branch is merged
ci_needUpgrade	CI: Need to upgrade next version after release branch is merged into default branch
ci_isPushed	CI: Check whether if auto commit is pushed to remote
ci_commitId	CI: auto commit id
ci_commitMsg	CI: auto commit message
ci_changelog_generated	CI: changelog is generated
ci_changelog_releaseTag	CI: changelog generated for release tag
ci_changelog_sinceTag	CI: changelog generated since tag
ci_changelog_isCommitted	CI: changelog is committed
ci_changelog_commitId	CI: changelog auto commit id
ci_changelog_commitMsg	CI: changelog auto commit message
decision_build	Decision: Should run the next step: such as build & test. Default value: !(ciPushed || isClosed || isMerged || (isBranch && (isRelease || isOpened)) || isAfterMergedReleasePR)
decision_publish	Should publish artifact: such as push artifact to any registry. Default value: decision.build && (onDefaultBranch || (isRelease && isTag))
ver_current	Current version in config file
ver_bumped	Bumped version
ver_nextMajor	Suggest next major version if after release and ver_current is compatible with semver
ver_nextMinor	Suggest next minor version if after release and ver_current is compatible with semver
ver_nextPatch	Suggest next patch version if after release and ver_current is compatible with semver

Note

Latest commit message

commitMsg is not available by default when synchronize/open pull-request. In case, you want to use the latest commit message in pull-request, need to tweak your build as below:

- uses: actions/checkout@v2with:
token: ${{ secrets.YOUR_GITHUB_TOKEN }}fetch-depth: 2
- uses: zero88/gh-project-context@v2

Use Cases

TBD