-
Notifications
You must be signed in to change notification settings - Fork 125
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
README instructions and photo are slightly contradictory #883
Comments
Hi, Julian! The landscape started its development 6 years ago, and no one could guess where it will lead to! Please use your favourite approach, "allow squash merging", it is a best one so far! Feel free to make a PR for a change to the README and, please, metion me, @AndreyKozlov1984 , when you create it, I'll be happy to merge! |
Amazing, thanks for the quick response and congrats on the success! PR sent in #884! |
Closes: cncf#883 Signed-off-by: Julian Berman <[email protected]>
Closes: cncf#883 Signed-off-by: Julian Berman <[email protected]>
(Hi! Thanks, nice looking tool. Just a very minor incongruity I figured I'd mention in case it's useful)
The setup instructions say:
But the screenshot shown just below show the opposite, checking only squash merges:
I don't personally generally recommend doing that in a git repo, but if there's some reason why landscapes really do need to always merge using squash then probably the simple fix is to just tweak the text above to say "squash merge" rather than "merge". Happy to send a PR if so, but filing this first since I wasn't sure which is actually correct, the text or the image, or whether really this step isn't actually required.
The text was updated successfully, but these errors were encountered: