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

[Feature]:Improving GitHub Actions: Preventing Improper Overwrites of Commit Messages #296

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

miura-toshihiko
Copy link

When using open commit in GitHub Actions, there is a problem that commit messages can be overwritten even if they are already correctly written.

So, we've added a new feature that allows you to set conditions for commit messages that should not be overwritten inappropriately (e.g., unusually short).

Added the ability to define illegal commit messages with regular expressions.
This logic works only with GitHub Actions.

The default condition is to use open comit only for very short commit messages as follows

OCO_INVALID_COMMIT_TITLE_REGEX: ^. {0,5}
OCO_INVALID_COMMIT_DESCRIPTION_REGEX: ^. {0,5}

…ssages

When using open commit in GitHub Actions, there is an issue where it overwrites even if there is already a precisely written commit message.

Therefore, we have made it possible to set conditions for commit messages that should not be overwritten improperly (such as being abnormally short).
@di-sukharev di-sukharev changed the base branch from master to dev March 3, 2024 11:23
@di-sukharev
Copy link
Owner

how does it overwrite commit messages that were already improved? i remember writing code that improves only new commit message, it shouldn't touch already improved messages. i think we can come up with a better implementation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants