Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): v2.2.0 #193

Draft
wants to merge 58 commits into
base: main
Choose a base branch
from
Draft

chore(release): v2.2.0 #193

wants to merge 58 commits into from

Conversation

Falcion
Copy link
Owner

@Falcion Falcion commented Nov 23, 2024

Before writing anything about your changes in this pull request, checklist these items:

Keep in mind security issues:

  • Read and accept the privacy and confidentiality agreements regarding security issues and personal data in accordance with the security policy.
    Read security policy here.

By agreeing 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 publish your pull request:

  1. In the case of “de-followization” of commit's styling convention, you can amend them (change their message and description signatures):

    git commit --amend -m "MESSAGE" -m "DESCRIPTION"

For amending old commit, see the stackoverflow question, 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/

  1. In the case of “de-followization” of coding, documentation etc. files, you can just refactor everything you need by following the styling guidelines of for a project.

Changes made with that pull request

Please, write below every changes you made:
...

Process of testing for that pull request

  • Was testing process initiated via this PR?
    answer (y/n): (n);
  • If testing was done, type below the procedures you make:
    ...

Additional context for that pull request

...

Last tags were "crashed" upon each other and because of this, "merge" tags were required: last of them, "v2.1.6" was a merge tag, meaning it doesn't have anything, but it is required to fix semantic versioning.

Fix of #179
Supports "lint-staged" project (created by them).

Fix of #189
Now "versioning" script supports updating issues functionality by folder and checking specified id of dropboxes.

Partially fix of #181
HUSKY yet again throwns same error with different solution to it, read the specified docs to it.
In this case, update-index was used.
@Falcion Falcion linked an issue Nov 23, 2024 that may be closed by this pull request
3 tasks
@Falcion Falcion marked this pull request as draft November 23, 2024 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment