Skip to content
This repository has been archived by the owner on Jun 13, 2023. It is now read-only.

Community and Support imporvements #11

Open
Nekroze opened this issue Feb 6, 2018 · 6 comments
Open

Community and Support imporvements #11

Nekroze opened this issue Feb 6, 2018 · 6 comments
Labels
enhancement New feature or request question Further information is requested

Comments

@Nekroze
Copy link
Contributor

Nekroze commented Feb 6, 2018

To ease contributions Gandalf should have a CONTRIBUTING.md file to explain any guide lines, this issue is to discuss and formulate what should be in that document as it too should be a community effort.

@Nekroze Nekroze added enhancement New feature or request help wanted question Further information is requested labels Feb 6, 2018
@patrickgordon
Copy link
Member

patrickgordon commented Feb 6, 2018

a proposed workflow would be useful.
e.g. fork, change code, PR

@Nekroze
Copy link
Contributor Author

Nekroze commented Feb 8, 2018

I would suggest creating a new branch post fork but that is good @patrickgordon

@Nekroze
Copy link
Contributor Author

Nekroze commented Feb 8, 2018

@patrickgordon seems we have just described github flow together

@Nekroze
Copy link
Contributor Author

Nekroze commented Feb 19, 2018

seems like it would also be worth mentioning some best practice recommendations for maintaining a fork on github similar to what is outlined here https://gist.github.com/yannvery/497ccbf26e4a71e8ad50 although I think the merge could be done better

@Nekroze
Copy link
Contributor Author

Nekroze commented Mar 27, 2018

would like all merging of PR's to be done with the Rebase and Merge option

@Nekroze Nekroze changed the title Guide to CONTRIBUTING.md Community and Support imporvements Mar 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants