You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read the template completely before filling it in.
Context
We should update Documentation: Every new PR should be included in the Dev Branch.
I mistakenly wrote in the documentation, that Fixes should be merged into Main and Improvements should be merged into Dev, but I think we should ALWAYS merge every PR into dev-Branch. In the longer term we should merge from DEV -> MAIN only when a new release is done.
What do you think? I would update the documentation accordingly.
Current Behavior
Different process for a FIX and FEATURE.
Expected behavior
ONE process for every change.
Possible Solutions or Causes
Base PRs always from dev branch.
Your Environment
No response
The text was updated successfully, but these errors were encountered:
Before submitting...
Context
We should update Documentation: Every new PR should be included in the Dev Branch.
I mistakenly wrote in the documentation, that Fixes should be merged into Main and Improvements should be merged into Dev, but I think we should ALWAYS merge every PR into dev-Branch. In the longer term we should merge from DEV -> MAIN only when a new release is done.
What do you think? I would update the documentation accordingly.
Current Behavior
Different process for a FIX and FEATURE.
Expected behavior
ONE process for every change.
Possible Solutions or Causes
Base PRs always from dev branch.
Your Environment
No response
The text was updated successfully, but these errors were encountered: