honkinggoose / git-gosling Goto Github PK

• Explain what kinds of files are usually ignored.
• Explain how to keep unwanted files from being committed with git commit with .gitignore.
• Explain .gitignore syntax.
• Add link to GitHub provided .gitignore starter templates.

Bijvoorbeeld: "ls --all" werkt niet op mac, dat moet "ls -A" zijn.
Hier een comment over maken aan het begin.

• Link to chapter 3 of ProGit2 book.
• Tell them to check Figure 10 especially, as that is a visual representation of what git commits are about. (They all relate to the root commit).

I'm not going to write about the GitHub CLI right now, so I'm removing the mentions of it in this project.

It will only be mentioned as a tip somewhere in the guide.

• Search for gh and GitHub CLI in docs.
• Remove mentions of learning gh from docs.
• Check README.
• Check tags.
• Check repo description.

• Create empty repo Github with name sandbox
• Add GitHub repo as remote origin/main
• Push local work to remote (GitHub)
• Explain the whole remote origin/main main thing

Think about what kind of branding images/supporting images/styling/logos are needed to give this project some personality.

Currently everything is default Docusaurus theming and branding.

Required:

• Small logo for project for sidebar
• Larger logo for homepage and README (Hero image)
• Favicon based on small logo
• Cleaner color scheme

Nice to have:

• Image of gosling growing up into goose.
• Improve features section by adding some more features + figure out appropriate images.

Doing a git add --patch right at the beginning is confusing for newcomers, so I'm going to:

• Move git add --patch to best practices section.
• Check text, simplify by just doing a git add . to stage the entire file at once.
• Add TIP pointing to git add --patch in best practices.

• Explain how to use git diff to compare branches.

• Clarify version of Git must be 2.25 or higher.

$ git config --global init.defaultBranch main

• Mention GitHub CLI as a way to do many GitHub operations from the command line, and provide link to gh official webpage.

Toevoegen van een up to date cheat sheet met veel gebruikte commands

• Create a new branch in the sandbox repo
• Add tip explaining why most repo's have a master branch, and how to change the branch name.
• Add tip: point to advanced configuration section to change default branch name for git init

Zou je mij ook bewerkrechten kunnen geven
Met bewerkrechten bedoel ik de mogelijkheid om kaartjes aan te maken en aan te passen.

Voor het geval dat je morgen graag wil terug vallen op de besproken flow, zet ik hem hieronder voor je weg:

Iedereen maakt een eigen repo

• Git init, git status
• Git add, git commit
• Git add: na een locale aanpassing
  (Git add -p)

Branches

• Git branch
• Git switch
  (Daarna: git switch create)
• Git merg

Naar Github

• Werk pushen naar een lege repo op github
• Maak op github iets aan: git pull
• Maak een locale verandering: git push

Git pull request

This issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update npm to v7

• Check this box to trigger a request for Renovate to run again on this repository

• git status see that git status lies to you
• git fetch --all --prune first to fetch latest changes from remote
• git status see that git status shows proper state
• git merge origin/main main so that they see the process
• Explain what a fast-forward merge is
• git pull is just a way to do git fetch and git merge in one command
• Add tip, point to advanced git configuration for git pull complaints about pull.rebase variable not being set.

• apt install nano
• dnf install nano

Is your feature request related to a problem? Please describe.
When maintaining a fork of a project the command $git status will compare the local main branch with origin/main.
However it will not check upstream/main.

Describe the solution you'd like
Create documentation to explain how to test for updates in the upstream repository.

• Read Docusaurus v2 docs on enabling Algolia
• Read Algolia docs
• Fix filename/directory structure so search can work properly (#49)
• Implement JavaScript snippet that Algolia provides

• Show how to merge feature branch into main branch
• Cover merge conflicts in short blurb.

• git log --all --decorate --oneline --graph
• git log --no-merges to not have merge commits
• git log --since=midnight
• git log --author=<pattern>, pattern is regular expression, only enter what you need to get unique match.

It might be handy to cover git bisect usage.

This should go in the advanced topics section.

• Short blurb about what git bisect is.
• Explain you can use it with automated tests or with manual approval.
• Link to ProGit2 book section on git bisect
• See if there's a playground type website/tutorial that covers git bisect

• Make edit from within GitHub interface.
• Show that you can change the branch name from the default patch-1.
• Make a pull request in the GitHub interface.
• Merge pull request from interface.
• Add tip about cleaner merge options: rebase and squash-merge.

• git switch to switch between branches
• TIP: git switch - to return to previous branch
• Cover git checkout as old way to switch branches, recommend readers use git switch first

Wat moeten medienten met de practice repo doen?

• git clone
• maak een issue met aanvraag md-file
• git pull
• HonkingGoose maakt kaartje en assigned de nodige medient.
• Medienten gaan aan de gang met de kaartjes
• HonkingGoose schrijft script.

Search engines do not show any description of the live website, it's probably to do with the tag.

Research proper fix, and implement it.

https://developer.mozilla.org/en-US/docs/Learn/HTML/Introduction_to_HTML/The_head_metadata_in_HTML#Active_learning_The_descriptions_use_in_search_engines

Ensure <h1> and .md filename are the same.
This also makes the links prettier and easier to read.

• Use separate directories per guide section if possible.
• Ensure .md filename and title are equal
• Fix best practices section
• Fix about this guide section
• Fix getting started with git section
• Fix nano introduction section
• Fix sandbox section
• Fix advanced topics section
• Fix further resources section

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Cover best practices to prevent big merges:

• TIP: Keep your changes small.
• TIP: Merge in work from mainline.
• TIP: Provide your work back to the mainline
• TIP: link to Martin Fowlers section on integration frequency for more on this.

Is your feature request related to a problem? Please describe.
The latest version as of writing (2.29.0) of git does not allow the use of:

git branch --set-upstream origin main

Git Gosling currently makes no mention of this in the section Create your first GitHub repo.

Describe the solution you'd like
Mention the newer syntax. In that context it should be:

git branch --set-upstream-to=origin/main

When creating new branches the --track option is used, although I have not tested this myself.

Describe alternatives you've considered

Additional context
Link to documentation: https://git-scm.com/docs/git-branch#Documentation/git-branch.txt---set-upstream-toltupstreamgt