docs: add Git branching best practices and optimize Netlify deployment instructions#29
Open
Grajales-K wants to merge 6 commits into
Open
docs: add Git branching best practices and optimize Netlify deployment instructions#29Grajales-K wants to merge 6 commits into
Grajales-K wants to merge 6 commits into
Conversation
Updated the success criteria to clarify that students should only deploy to Netlify once they reach Level 500. This change helps students avoid exhausting their Netlify build credits during the earlier stages of the project
Added best practices for Git branching and deployment. Encouraging students to use feature branches for Level 500 and deploy only after final merge to optimize Netlify usage.
illicitonion
reviewed
May 5, 2026
Member
illicitonion
left a comment
There was a problem hiding this comment.
Generally LGTM - let's avoid repeating the contents of the deployment guides here, so that if the steps need to change (e.g. if Netlify change their screens) we only need to update one place not multiple.
Author
|
Hi @illicitonion, thank you so much for carefully checking my changes. I have updated the file and removed the repetitive information that is already covered in the official documentation. I hope this is clearer now! |
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
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.
Revised PR Description
Problem: Currently, the instructions do not introduce GitHub Pages for early deployment, leading to unnecessary consumption of Netlify build credits. Additionally, the Level 500 instructions lack explicit guidance on feature branches and final deployment setup.
Changes:
Level 0: Replaced Netlify with GitHub Pages for initial deployment to provide a free, unlimited hosting option during early development.
Level 500: * Moved Netlify deployment instructions here as the final "production" step.
Added a detailed Step-by-Step guide for Netlify setup (since it was removed from Level 0).
Added a "Technical Workflow" section to encourage the use of feature branches (feature/level-500) after merging Level 400.
Aligned instructions with dashboard submission requirements to reduce student confusion.