From 2b192d8dfbd32777fb65243140872e0d6712d94e Mon Sep 17 00:00:00 2001 From: alex Date: Sun, 1 Mar 2026 18:19:45 +0100 Subject: Move GitHub annoyances to blog website --- blog/content/notes/index.gmi | 1 + blog/content/notes/tech/github-annoyances.gmi | 7 +++++++ 2 files changed, 8 insertions(+) create mode 100644 blog/content/notes/tech/github-annoyances.gmi (limited to 'blog/content/notes') diff --git a/blog/content/notes/index.gmi b/blog/content/notes/index.gmi index a1d71352..f16f0cb5 100644 --- a/blog/content/notes/index.gmi +++ b/blog/content/notes/index.gmi @@ -26,6 +26,7 @@ Notes about some books I like: => tech/crud-is-an-important-unsolved-problem CRUD is an important unsolved problem => tech/about-django About Django => tech/git-advice Git advice +=> tech/github-annoyances GitHub annoyances ### Gadgets diff --git a/blog/content/notes/tech/github-annoyances.gmi b/blog/content/notes/tech/github-annoyances.gmi new file mode 100644 index 00000000..a36214b9 --- /dev/null +++ b/blog/content/notes/tech/github-annoyances.gmi @@ -0,0 +1,7 @@ +# GitHub annoyances + +## The repository creation wizard can be confusing initially + +When creating a new repo, GitHub offers you to populate the repository with some files (a README, a .gitignore file, a license). + +In some situations, you have an existing directory in your computer with files that you want to be the initial contents of the repo. If you create a truly empty repo, then GitHub displays some instructions that can help pushing the contents of your existing directory to the new repo. If you use the GitHub features to populate the repo, then GitHub does not display these instructions and uploading your files requires more knowledge. -- cgit v1.2.3