Skip to content

chore: Add semantic pull requests #5

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

Merged
merged 4 commits into from
Jan 6, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Remove scopes
  • Loading branch information
bryphe-coder committed Jan 6, 2022
commit 82d657029639e398e4a4f0d4ad8145c7acd1d63e
18 changes: 0 additions & 18 deletions .github/semantic.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -7,24 +7,6 @@
# https://www.notion.so/coderhq/Conventional-commits-1d51287f58b64026bb29393f277734ed
###############################################################################

# Scopes are optionally supplied after a 'type'. For example, in
#
# feat(cdr): autostart ui
#
# '(cdr)' is the scope. Scopes are used to signify where the change occurred.
scopes:
# The Coder product (front/back/deploy) (path: product/coder)
- cdr

# The Coder CLI (path: product/coder/service/cli)
- cli

# The Coder product e2e suite (path: product/coder/e2e)
- e2e

# A change to a shared library module (path: lib/)
- lib

# We only check that the PR title is semantic. The PR title is automatically
# applied to the "Squash & Merge" flow as the suggested commit message, so this
# should suffice unless someone drastically alters the message in that flow.
Expand Down