Create README.md and Organizational Suggestions - #3
Open
seantrim wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Created a README file for the Nutrient App project. I have included the information I could find and added some suggested sections for future updates.
After merging with the master branch, I'd recommend changing the name of the primary branch from "master" to "main" in order to follow the most current practice. I have included Git instructions for how to update local clones after the name change is done (see Branches section in the new README).
I would also recommend creating a new branch named "development", that can be used to confirm the functionality of changes from feature branches (such as Retrieve_serverdata) before merging with "main".