README refactoring #231
Merged
README refactoring #231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
veroandreo
reviewed
Dec 5, 2019
|
|
||
| Want to become a core developer? See | ||
| [Procedure for gaining Git write access](https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheGRASScorerepository) | ||
|
|
||
| How to compile GRASS? | ||
| --------------------- | ||
| ## How to compile GRASS? | ||
|
|
||
| > See INSTALL file. | ||
|
|
||
| Yes, you should really read INSTALL. |
There was a problem hiding this comment.
To make it easier, I would put the link to this INSTALL file here and maybe also to the wiki: https://grasswiki.osgeo.org/wiki/Compile_and_Install
There was a problem hiding this comment.
Good point. I will do it in the next commit. I also think that there should be noted how to open a ticket/why the issues are still not available on git in the README.
neteler
pushed a commit
that referenced
this pull request
Dec 12, 2019
Follow Markdown recommended style guides in README: * Do not mix different header styles (minuses and hash marks were used for the same level) * Line length = 80 characters (I ignored the code excerpts parts) * Do not use plain URLs (use <URL> for them) * Delete unnecessary indentation * Surround fenced code blocks by blank lines * Delete multiple consecutive blank lines
landam
pushed a commit
to landam/grass
that referenced
this pull request
Jan 28, 2020
Follow Markdown recommended style guides in README: * Do not mix different header styles (minuses and hash marks were used for the same level) * Line length = 80 characters (I ignored the code excerpts parts) * Do not use plain URLs (use <URL> for them) * Delete unnecessary indentation * Surround fenced code blocks by blank lines * Delete multiple consecutive blank lines
petrasovaa
pushed a commit
to petrasovaa/grass
that referenced
this pull request
Feb 18, 2020
Follow Markdown recommended style guides in README: * Do not mix different header styles (minuses and hash marks were used for the same level) * Line length = 80 characters (I ignored the code excerpts parts) * Do not use plain URLs (use <URL> for them) * Delete unnecessary indentation * Surround fenced code blocks by blank lines * Delete multiple consecutive blank lines
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow Markdown recommended style guides in README:
<URL>for them)