By agreeding and following this project's documentation, you are reminded that your's commit and styling of changes must follow this project's documentation, in case of “de-followization”, there are two ways before you make sure to publishing your PR:
In case of “de-followization” of commit's styling convention, you can amend them (change their message and description signatures):
In case of “de-followization” of coding, documentation and etc. files, you can just refactor everything you need by following styling guidelines of project.
Changes with that PR
Please, write below every changes you made:
TITLE REF.
Process of testing for that PR
Was testing process initiated via this PR?\
answer (y/n): (n);
If testing was done, type below the procedures you make: \
...
PRs: edit manifest in order to describe new plugin's functionality
Before writing anything about your changes in this PR, checklist this items:
By agreeding and following this project's documentation, you are reminded that your's commit and styling of changes must follow this project's documentation, in case of “de-followization”, there are two ways before you make sure to publishing your PR:
For amending old commit, see the stackoverflow question^1, more about changing commits in official docs for github: \ https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message/
Changes with that PR
Please, write below every changes you made:
TITLE REF.
Process of testing for that PR
Additional contenxt for that PR
...