DHBW-WE/MeetUp
5
0
Fork 0
Code Issues 7 Pull requests 11 Projects 1 Releases 5 Packages 1 Wiki Activity Actions

docs: update contribution guidelines to standardize branch naming and commit message format #52

Merged
lima merged 1 commit from docs/51-branch_naming_scheme_in_readme into main 2025-05-12 11:22:12 +00:00
Conversation 2 Commits 1 Files changed 1 +15 -4
lima commented 2025-05-12 08:49:16 +00:00
Member
Copy link

closes #51

closes #51
lima added 1 commit 2025-05-12 08:49:16 +00:00
docs: update contribution guidelines to standardize branch naming and commit message format
All checks were successful
container-scan / Container Scan (pull_request) Successful in 1m10s
Details
docker-build / docker (pull_request) Successful in 3m17s
Details
df55014f3a
requested review from Contributor 2025-05-12 08:49:25 +00:00
dominik requested changes 2025-05-12 09:02:56 +00:00
Dismissed
README.md Outdated
@ -126,3 +126,3 @@
1. Fork the repository.
2. Create a new branch (`git checkout -b feature/your-feature-name` or `fix/your-bug-fix`).
2. Create a new branch (`git checkout -b action/<issue#>-feature_name`).
dominik commented 2025-05-12 09:02:48 +00:00
Owner
Copy link

Würde hier auch <action> machen, das klar ist, dass hier auch was ersetzt werden muss

Würde hier auch `<action>` machen, das klar ist, dass hier auch was ersetzt werden muss
lima marked this conversation as resolved
README.md Outdated
@ -133,0 +131,4 @@
5. Push to the branch (`git push origin action/<issue#>-feature_name`).
6. Open a Pull Request against the `main` branch.
Possible actions are: feat|fix|test|docs|chore|refactor|style|revert
dominik commented 2025-05-12 09:01:59 +00:00
Owner
Copy link

Possible actions are:

  • feat -> Feature added
  • fix -> Fixed a bug
  • test -> Modified or added tests
  • docs -> Modified documentation
  • chore -> changes to non code files (workflows, lock files, ...)
  • refactor -> rewritten code without changing functionality
  • style -> code style (yarn format)
  • revert -> reverts a previous commit
Possible actions are: - feat -> Feature added - fix -> Fixed a bug - test -> Modified or added tests - docs -> Modified documentation - chore -> changes to non code files (workflows, lock files, ...) - refactor -> rewritten code without changing functionality - style -> code style (`yarn format`) - revert -> reverts a previous commit
lima marked this conversation as resolved
lima added 1 commit 2025-05-12 09:07:01 +00:00
docs: update contribution guidelines for branch naming and commit message format
All checks were successful
container-scan / Container Scan (pull_request) Successful in 1m12s
Details
docker-build / docker (pull_request) Successful in 2m49s
Details
c7850b9c03
requested review from dominik 2025-05-12 09:08:27 +00:00
lima added 1 commit 2025-05-12 11:14:34 +00:00
docs: update contribution guidelines for branch naming and commit message format
All checks were successful
container-scan / Container Scan (pull_request) Successful in 1m15s
Details
docker-build / docker (pull_request) Successful in 3m3s
Details
94873ef79c
lima force-pushed docs/51-branch_naming_scheme_in_readme from 94873ef79c to 9aced187eb 2025-05-12 11:15:48 +00:00 Compare
dominik approved these changes 2025-05-12 11:16:05 +00:00
lima merged commit 86b9b9e6ad into main 2025-05-12 11:22:12 +00:00
lima deleted branch docs/51-branch_naming_scheme_in_readme 2025-05-12 11:22:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
dominik
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Review needed
  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Review needed
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DHBW-WE/MeetUp#52
No description provided.
Delete branch "docs/51-branch_naming_scheme_in_readme"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?