Replies: 10 comments
-
|
I think this would be a great addition to the curriculum! If anyone is interested in working on this please comment here and ping me. @Sankalp-G thank you for taking the time to create such a detailed issue! |
Beta Was this translation helpful? Give feedback.
-
|
@wise-king-sullyman I'm down to work on this! I haven't wrote a whole lesson before but this seems like a great opportunity. |
Beta Was this translation helpful? Give feedback.
-
|
@ArjunSaili1 you're assigned! As for next steps on this there are two options:
I'm perfectly happy with either approach you'd like to take, I just wanted to make sure you understand the pros/cons of each 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Hey @wise-king-sullyman, I think I'll that 2nd approach since this is my first time writing a lesson. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @wise-king-sullyman, let me know when you and the rest of the maintainer team come up with the basic requirements. Ready to start working on it as soon as possible :) |
Beta Was this translation helpful? Give feedback.
-
|
@ArjunSaili1 thanks! Sorry, but I've been extremely busy this past week and haven't been able to plan on it much yet. This is high on my todo list though! |
Beta Was this translation helpful? Give feedback.
-
|
@wise-king-sullyman No worries |
Beta Was this translation helpful? Give feedback.
-
|
@ArjunSaili1 the question of where to add this content has actually caused a bit of debate, and we're currently re-evaluating how we structure our Git content because of that. Until we can do some investigation and come to a decision on that front this issue will, unfortunately, have to be on hold, but I will reach out to you once we're ready to move forward with it 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
This issue is stale because it has had no activity for the last 30 days. |
Beta Was this translation helpful? Give feedback.
-
|
This issue is stale because it has had no activity for the last 30 days. |
Beta Was this translation helpful? Give feedback.
-
Complete the following REQUIRED checkboxes:
location for request: brief description of requestformat, e.g.NodeJS course: Add lessons on XYZThe following checkbox is OPTIONAL:
1. Description of the Feature Request:
Git Branches are an essential part of the git workflow and the 'how' and 'why' to use branches is covered very well in the rock paper scissor revisit.
But it can be difficult for a learner to judge when or how frequently one should use branches in their project.
The RPS revisit lesson briefly states that you should use a branch when adding a new feature, however it is still quite unclear what qualifies as a feature.
thus a lot of learners might neglect using branches, especially in backend focused paths where most of your progress is made in small chunks, making it a lot harder to know when the right time to branch is.
Introducing a lesson/section going over topics such as frequency of branches, considering how to divide parts of the project into individual feature branches, basic nomenclature as well as a few examples could be of great help for learners to get accustomed to the git branching workflow.
these are all concepts that aren't focused on in the curriculum and are also hard to notice even when done incorrectly, thus having a proper guide can be greatly beneficial.
2. Acceptance Criteria:
A lesson or section that covers:
3. Additional Information:
This issue came to light from a discussion on the discord server between me(AstralX) and BriggsE given here.
A lesson like this could be suitable either a bit after RPS or near the start of the language specific paths.
Beta Was this translation helpful? Give feedback.
All reactions