Create setup.md #510
Create setup.md #510
Conversation
|
||
Run each of those, and wait for them to install. | ||
Next, open git bash and run the following: | ||
git clone you will need to download the following files: |
Lupus590
Jan 25, 2018
•
Contributor
i think you have a copy paste error or something here
i think you have a copy paste error or something here
JasonTheKitten
Jan 26, 2018
Author
Yea I did have a copy/paste error. A few, in fact
Yea I did have a copy/paste error. A few, in fact
I'm going to be honest, I do feel this is overly complicated for what equates to:
Have a look at some of Dan's comments on #290 as well - one doesn't need to spoon feed it to the user. |
@JasonTheKitten You want to make things easier, and I can respect that. The issue is that once you've used Gradle once, it's the same elsewhere. I don't think we need to serve as an introduction to Gradle, just provide a couple of simple steps and link to something like this should people more information. With respect to CC specific build steps, we should probably mention |
And to save pain later say something like this. "If there is no |
I use windows cmd not linux bash so I can't use sh files |
What does that mean? If you mean it makes new gradle files, then can't we just use copy/paste instead of the git command? Or delete the new folders? |
Once you've set up Gradle in your editor once, it's pretty much the same procedure in any other project which uses Gradle. |
@JasonTheKitten are you aware that you still have this pull request open and you have made a commit against it which seems irrelevant to the pull request? |
That was an accident I don't really expect this to be merged though. Also, is their a way to change/undo files/commits without it incrementting the commit counter? |
https://sethrobertson.github.io/GitFixUm/fixup.html You will need to force the push, after following the steps in the above link, do this with Also, check which branch you are committing to before you start editing things. |
Force pushing is a bad idea. If you've already pushed erroneous commits (which you have) you should just revert the changes instead. When merging the commits can be squashed or cherry picked if dan is worried about extra commits. |
Reverting leaves a revert commit which makes the PR much harder to review. Force push is perfectly valid for PRs |
The files changed tab (usually used for reviews) will not show the difference because the changes are reverted, and the extra commits can be dropped when merging. |
Can one of the admins verify this patch? |
Back-Merge
This is so that people know how to set it up