I have multiple links that are provided in the various docs and posts. The most useful links so far are:
The forum link above mentions:
- Perform the maintenance step of rebasing
I have no idea what to do with rebasing unless that is what I did with all these commands from the 2nd link:
git fetch upstream git reset --hard upstream/main git push origin main –force git diff upstream/main
Regardless, there is no
staging branch. Using the git command
git branch -a, this is what I get:
* main remotes/origin/HEAD -> origin/main remotes/origin/fix/lowercasing remotes/origin/i18n-sync-client remotes/origin/i18n-sync-curriculum remotes/origin/i18n-sync-docs remotes/origin/main remotes/origin/prod-current
Question #1: So why do I need to be on the staging branch? In the md file link above it says to “Create a fresh new branch”. I’d rather do that since that is what I thought you are supposed to do.
Question #2: It also suggests using names like
fix/update-guide-for-xyz and some choices are fix/, feat/, docs/. What would be a good prefix for typos or changes in wording?
I found a number of mistakes in the beta web-design course. The first one I wanted to do was to remove the word “is” because it is in the lesson by accident. ONE WORD! I’ve been looking at all the linked pages and docs and instructions for over an hour, and I think I’m going to be at it for at least another hour…to change ONE WORD. Is this how all repos are set up for contributions? Is there a cliff notes version that has a simple step guide?
One more thing: When and if I figure all this out, should I do a commit with a description? If so, how to you add a description?