Skip to content

CI/Documentation: Handling Pull Requests #367

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

Closed
3 tasks done
wuda-io opened this issue May 9, 2023 · 1 comment
Closed
3 tasks done

CI/Documentation: Handling Pull Requests #367

wuda-io opened this issue May 9, 2023 · 1 comment

Comments

@wuda-io
Copy link
Member

wuda-io commented May 9, 2023

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

@DanielRuf
Copy link

In the longer term we should merge from DEV -> MAIN only when a new release is done.

Exactly my thought.

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

No branches or pull requests

2 participants