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

feat: give helpful messages in pr #2

Merged
merged 4 commits into from
Jan 25, 2022
Merged

feat: give helpful messages in pr #2

merged 4 commits into from
Jan 25, 2022

Conversation

levibostian
Copy link
Owner

No description provided.

@levibostian-oss-bot
Copy link

levibostian-oss-bot commented Jan 25, 2022

Pull request title looks good 👍. It's ready to merge after all other steps have been taken.

@levibostian levibostian changed the title feat: give helpful messages in pr invalid title feat: give helpful messages in pr Jan 25, 2022
@levibostian-oss-bot
Copy link

Hey, there @levibostian 👋🤖. I'm a bot here to help you.

This project uses a special format for pull requests titles. Don't worry, it's easy!

This pull request title should be in this format:

<type>: short description of change being made

where <type> is one of the following:

  • feat: - A new feature is being added by this pull request.

  • fix: - A bug is being fixed by this pull request.

  • docs: - This pull request is making documentation changes, only.

  • refactor: - A change was made that doesn't fix a bug or add a feature.

  • test: - Adds missing tests or fixes broken tests.

  • style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

  • perf: - Changes improve performance of the code.

  • build: - Changes to the build system (maven, npm, gulp, etc)

  • ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

  • chore: - Other changes to project that don't modify source code or test files.

  • revert: - Reverts a previous commit that was made.

If your pull request causes breaking changes to the code base, you need to add a ! after the <type>: feat!: remove deprecated v1 endpoints

Examples
``` feat: edit profile photo feat!: remove deprecated v1 endpoints build: update npm dependencies style: run formatter ```

Need more examples? Want to learn more about this format? Check out the official docs.

Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests. Small and focused pull requests are preferred by the reviewers of the code.

@levibostian levibostian changed the title invalid title feat: give helpful messages in pr feat: give helpful messages in pr Jan 25, 2022
@levibostian levibostian merged commit 390773a into develop Jan 25, 2022
@levibostian levibostian deleted the helper-text branch January 25, 2022 20:54
github-actions bot pushed a commit that referenced this pull request Jan 26, 2022
# 1.0.0 (2022-01-26)

### Bug Fixes

* adding label to merged pr ([2230661](2230661))

### Features

* give helpful messages in pr ([#2](#2)) ([390773a](390773a))
* lint PR title against rule set ([#1](#1)) ([3d0d97c](3d0d97c))
* merge PR by adding label ([0ff85b7](0ff85b7))
* suggest if pr will make a new release ([712ce36](712ce36))
@levibostian-oss-bot
Copy link

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants