PR title/commit message must follow convention: <type>(<scope>): <subject>.
Most common types are:
* `feat` - for new features, not a new feature for build script
* `fix` - for bug fixes or improvements, not a fix for build script
* `chore` - changes not related to production code
* `docs` - changes related to documentation
* `style` - formatting, missing semi colons, linting fix etc; no significant production code changes
* `test` - adding missing tests, refactoring tests; no production code change
* `refactor` - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes
IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.
updating branch reference from master to develop in following files:
CONTRIBUTING.md
GOVERNANCE.md
README.md
RELEASE.md
buildscripts/install-test-dep.sh
code-standard.md
developer-setup.md
chore(workflow): push images to ghcr
Signed-off-by: mayank mayank.patel@mayadata.io
Pull Request template
Please, go through these steps before you submit a PR. ## Remove this line
Why is this PR required? What issue does it fix?:
What this PR does?:
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered and commands you used for testing with logs:
Any additional information for your reviewer?: Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>
PLEASE REMOVE THIS TEMPLATE BEFORE SUBMITTING
PR title/commit message must follow convention:
<type>(<scope>): <subject>
.IMPORTANT: Please review the CONTRIBUTING.md file for detailed contributing guidelines.