From 1becb20695f6a8b912bcde4c5d46d156654e6c58 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Thu, 9 Jan 2025 13:46:19 +0000 Subject: [PATCH] site deploy Auto-generated via `{sandpaper}` Source : b8a8b6c66cf2bf720fa5654a51830f6248223b59 Branch : md-outputs Author : GitHub Actions Time : 2025-01-09 13:45:59 +0000 Message : markdown source builds Auto-generated via `{sandpaper}` Source : 055b9e762f57beba02a4c2dfa39db1324e7c3e7b Branch : main Author : Dimitrios Theodorakis Time : 2025-01-09 13:44:20 +0000 Message : #39 Modifies the lesson to work on one repo throughout --- 00-repo-access.html | 549 ++++++++++ 01-issues.html | 146 ++- 02-branching.html | 79 +- 03-feature-branch.html | 385 ++++--- 04-review.html | 173 ++-- 05-forks.html | 302 +++--- 06-conflict.html | 73 +- 07-history.html | 82 +- 08-rebase.html | 64 +- 09-pre-commit.html | 57 +- 404.html | 51 +- Break.html | 76 +- CODE_OF_CONDUCT.html | 47 +- End.html | 72 +- LICENSE.html | 47 +- aio.html | 908 ++++++++++------- config.yaml | 5 +- discuss.html | 47 +- fcm-git_cheat_sheet.html | 47 +- fig/feature-branch-1-dark.png | Bin 45558 -> 81048 bytes fig/feature-branch-1.png | Bin 44278 -> 80215 bytes fig/feature-branch-2-dark.png | Bin 34921 -> 38449 bytes fig/feature-branch-2.png | Bin 35425 -> 37615 bytes fig/github-collaboration.svg | 10 +- fig/github-fork-pr-open-dark.png | Bin 0 -> 54934 bytes fig/github-fork-pr-open.png | Bin 0 -> 53933 bytes ...tification-invitation-join-repo-2-dark.png | Bin 0 -> 66059 bytes ...ub-notification-invitation-join-repo-2.png | Bin 0 -> 62630 bytes ...notification-invitation-join-repo-dark.png | Bin 0 -> 59860 bytes ...thub-notification-invitation-join-repo.png | Bin 0 -> 55452 bytes fig/github-pr-review-request-dark.png | Bin 0 -> 62693 bytes fig/github-pr-review-request.png | Bin 0 -> 62555 bytes fig/pr-1-dark.png | Bin 35741 -> 34747 bytes fig/pr-1.png | Bin 35119 -> 34496 bytes fig/pr-2-dark.png | Bin 55459 -> 45106 bytes fig/pr-2.png | Bin 55510 -> 45161 bytes fig/pr-3-dark.png | Bin 70640 -> 54889 bytes fig/pr-3.png | Bin 70031 -> 54116 bytes fig/pr-4-dark.png | Bin 29604 -> 24694 bytes fig/pr-4.png | Bin 28707 -> 24007 bytes fig/pr-review-1-dark.png | Bin 136632 -> 205027 bytes fig/pr-review-1.png | Bin 133139 -> 203179 bytes fig/pr-review-2-dark.png | Bin 26922 -> 75043 bytes fig/pr-review-2.png | Bin 27420 -> 77003 bytes fig/pr-review-3-dark.png | Bin 31714 -> 26673 bytes fig/pr-review-3.png | Bin 30224 -> 25934 bytes fig/pr-review-4-dark.png | Bin 64272 -> 55960 bytes fig/pr-review-4.png | Bin 63176 -> 55828 bytes fig/pr-review-5-dark.png | Bin 42746 -> 40381 bytes fig/pr-review-5.png | Bin 41713 -> 40119 bytes fig/pr-review-6-dark.png | Bin 18369 -> 17810 bytes fig/pr-review-6.png | Bin 17626 -> 17022 bytes fig/pr-review-7-dark.png | Bin 122937 -> 34480 bytes fig/pr-review-7.png | Bin 120069 -> 32946 bytes fig/pr-rich-diff-dark.png | Bin 10530 -> 13502 bytes fig/pr-rich-diff.png | Bin 9942 -> 13094 bytes fig/pr-suggestion-2-dark.png | Bin 53843 -> 52700 bytes fig/pr-suggestion-2.png | Bin 51650 -> 50434 bytes fig/pr-suggestion-dark.png | Bin 31330 -> 24233 bytes fig/pr-suggestion.png | Bin 31111 -> 23579 bytes images.html | 97 +- index.html | 117 +-- instructor-notes.html | 52 +- instructor/00-repo-access.html | 551 ++++++++++ instructor/01-issues.html | 160 ++- instructor/02-branching.html | 79 +- instructor/03-feature-branch.html | 385 ++++--- instructor/04-review.html | 173 ++-- instructor/05-forks.html | 322 +++--- instructor/06-conflict.html | 75 +- instructor/07-history.html | 82 +- instructor/08-rebase.html | 64 +- instructor/09-pre-commit.html | 57 +- instructor/404.html | 51 +- instructor/Break.html | 76 +- instructor/CODE_OF_CONDUCT.html | 47 +- instructor/End.html | 72 +- instructor/LICENSE.html | 47 +- instructor/aio.html | 946 ++++++++++-------- instructor/discuss.html | 47 +- instructor/fcm-git_cheat_sheet.html | 47 +- instructor/images.html | 97 +- instructor/index.html | 173 ++-- instructor/instructor-notes.html | 70 +- instructor/key-points.html | 90 +- instructor/profiles.html | 158 ++- instructor/reference.html | 47 +- key-points.html | 90 +- md5sum.txt | 27 +- pkgdown.yml | 2 +- profiles.html | 158 ++- reference.html | 47 +- sitemap.xml | 6 + 93 files changed, 4908 insertions(+), 2824 deletions(-) create mode 100644 00-repo-access.html create mode 100644 fig/github-fork-pr-open-dark.png create mode 100644 fig/github-fork-pr-open.png create mode 100644 fig/github-notification-invitation-join-repo-2-dark.png create mode 100644 fig/github-notification-invitation-join-repo-2.png create mode 100644 fig/github-notification-invitation-join-repo-dark.png create mode 100644 fig/github-notification-invitation-join-repo.png create mode 100644 fig/github-pr-review-request-dark.png create mode 100644 fig/github-pr-review-request.png create mode 100644 instructor/00-repo-access.html diff --git a/00-repo-access.html b/00-repo-access.html new file mode 100644 index 0000000..3cacdf9 --- /dev/null +++ b/00-repo-access.html @@ -0,0 +1,549 @@ + +Git Working Practices: Repository Access +
+ Git Working Practices +
+ +
+
+ + + + + +
+
+

Repository Access

+

Last updated on 2025-01-09 | + + Edit this page

+ + + +
+ +
+ + + +
+

Overview

+
+
+
+
+

Questions

+
  • What levels of repository permissions are there?
    • +
+
+
+
+
+
+

Objectives

+
  • Know how to give a collaborator access to your repository.
    • +
+
+
+
+
+

To be able to contribute to the git-training-demo +repository your instructors will have to give you access. They are going +to showcase this now. The steps are:

+

In the repository page on GitHub, click the “Settings” button on the +right, select “Collaborators”, click “Add people”, and enter a +username/s.

+
A screenshot of the GitHub Collaborators settings page, which is accessed by clicking "Settings" then "Collaborators".
A screenshot of the GitHub Collaborators +settings page for a public personal repository, which is accessed by +clicking “Settings” then “Collaborators”.
+

To accept access to the repository, you will need to go to https://github.com/notifications +or check for an email notification. Once there you can accept access to +the repository.

+

Permission Levels

+
+

Personal Repositories

+

Repositories on personal accounts only have two levels of +permissions, the Owner and Collaborators1. To use the branching +model in this lesson you would need adding as a collaborator. You can +still contribute to a public repository without being added as a +collaborator by using the forking model.

+
+
+

Organisational Repositories

+

Repositories in organisations have more levels of permissions2. Team +members require at least write access to use the +branching model. For all lower levels of access use the forking +model.

+
+
+ +
+
+

Key Points

+
+
+
+
+
+
+

  1. The GitHub +documentation has more information on permissions for a repository +on a personal account.↩︎

    2. +

  2. The GitHub +Documentation has more information on the different permission +levels for repositories in organisations.↩︎

    3. +
+ + + +
+
+ + +
+
+ + + diff --git a/01-issues.html b/01-issues.html index 47494ee..e134c86 100644 --- a/01-issues.html +++ b/01-issues.html @@ -18,13 +18,13 @@
-