Adds 2 new labs and updates the readme

CalinL · CalinL · commit 2a1a6a1df2cb · 2023-02-16T15:00:49.000-05:00
diff --git a/.github/workflows/use-github-apis.yml b/.github/workflows/use-github-apis.yml
@@ -0,0 +1,71 @@
+name: 05-1. Use GitHub APIs
+on: 
+  workflow_dispatch:
+  push:
+
+# Limit the permissions of the GITHUB_TOKEN
+permissions:
+  contents: read
+  issues: write
+
+jobs:
+
+  rest-api-create-and-close-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v6
+        id: create-issue
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            const result = await github.rest.issues.create({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              title: 'Issue auto-created from workflow run ${{github.run_id}}',
+              body: '👋 Thank you! We appreciate your contribution to this project.',
+              labels: ["training"]
+            })
+            console.log(result)
+            return result.data
+
+      - name: Displays create issue result
+        run: echo "${{toJSON(steps.create-issue.outputs.result)}}"
+
+      # Add here the close-issue step
+
+
+  graphql-api-query-issues:
+    needs: rest-api-create-and-close-issue
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v6
+        id: issues-result
+        with:
+          script: |
+            const query = `query($owner:String!, $name:String!, $label:String!) {
+              repository(owner:$owner, name:$name){
+                issues(first:100, labels: [$label]) {
+                  nodes {
+                    number,
+                    title
+                  }
+                }
+              }
+            }`;
+            const variables = {
+              owner: context.repo.owner,
+              name: context.repo.repo,
+              label: 'training'
+            }
+            const result = await github.graphql(query, variables)
+            console.log(result.repository.issues.nodes)
+            return result
+      
+      - name: Displays training issues
+        run: echo "${{toJSON(steps.issues-result.outputs.result)}}"
+
+  
+  # Add here the labels query step
+
+
+            
diff --git a/README.md b/README.md
@@ -15,6 +15,12 @@
 ### Module 3: Managing a branch protection rule
 - [ ]  _Hands-on Lab:_ > [Activity 3](/labs/lab03.md)
 
+### Module 4: GitHub Templates
+- [ ]  _Hands-on Lab:_ > [Activity 2](/labs/lab04.md)
+
+### Module 5: GitHub API
+- [ ]  _Hands-on Lab:_ > [Activity 5](/labs/lab05.md)
+
 ---
 
 ## Additional Resources
@@ -31,6 +37,10 @@
 - [Repositories](https://docs.github.com/en/enterprise-cloud@latest/repositories)
 - [Roles in an organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#permission-levels-for-an-organization)
 - [Configuring SCIM provisioning for Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)
+- [About Enterprise Managed Users](https://docs.github.com/en/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users)
+- [Managing a branch protection rule](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)
+- [GitHub Blog Enterprise](https://github.blog/category/enterprise/)
+- [GitHub Actions - Security guides](https://docs.github.com/en/actions/security-guides)
 
 ### Admin Changelog
 - [GitHub Changelog](https://github.blog/changelog/)
@@ -41,9 +51,13 @@
 - [What's new for GitHub Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube-nocookie.com/embed/ZZviWZgrqhM)
 - [GitHub in the Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube.com/watch?v=1-i39RqaxRs)
 - [Enforcing information security policy through GitHub Enterprise - GitHub Universe 2021 - YouTube](https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI)
+- [GitHub Universe](https://githubuniverse.com/)
 
 ### Articles & Guides
+- [Everything new from GitHub Universe 2022](https://github.blog/2022-11-09-everything-new-from-github-universe-2022/)
 - [Improved management for GitHub Enterprise owners | The GitHub Blog](https://github.blog/2022-03-10-improved-management-github-enterprise-owners/)
 - [How to secure your GitHub organization and enterprise account | The GitHub Blog](https://github.blog/2020-07-23-how-to-secure-your-github-organization-and-enterprise-account/)
 - [Connect GitHub Enterprise Cloud to Defender for Cloud Apps | Microsoft Docs](https://docs.microsoft.com/en-us/defender-cloud-apps/connect-github-ec)
-- [How Defender for Cloud Apps helps protect your GitHub Enterprise environment | Microsoft Docs](https://docs.microsoft.com/en-us/defender-cloud-apps/protect-github)
+- [How Defender for Cloud Apps helps protect your GitHub Enterprise environment | Microsoft Docs](https://docs.microsoft.com/en-us/defender-cloud-apps/protect-github)
+- [GitHub Workflow Guide](https://github.github.com/services-workflow-guide/#/)
+- [Removing sensitive data from a repository - GitHub Docs](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)
diff --git a/labs/lab04.md b/labs/lab04.md
@@ -0,0 +1,51 @@
+# 4 - GitHub Templates
+In this lab you will create issue and pull request templates and make an existing repository a template.
+> Duration: 5-10 minutes
+
+References:
+- [Issue & pull request templates](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests)
+- [Configuring issue templates for your repository](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)
+- [Creating a pull request template for your repository](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)
+- [Creating a template repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository)
+- [Creating a repository from a template](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template)
+
+## 2.1 Create issue templates
+
+1. Navigate to the `Settings > General` page of your repository
+2. In the `Features > Issues` section, click `Set up templates` button
+3. Select a template from the list
+4. Review the template by clicking on `Preview and edit`
+5. Edit the issue if needed to add your changes
+6. Click on `Propose changes` to commit the tempaltes to your repository. 
+7. Repeat steps 3) to 6) to add more issue templates
+
+## 2.2 Create pull request templates
+
+1. Navigate to the `main` branch of your repository
+2. Click `Add file` to create a new file
+3. Name the file `.github/pull_request_template.md`
+4. In the body of the file, add your template:
+5. `Propose new file` and commit it directly to the `main` branch
+```markdown
+Fixes #
+
+### Changes proposed with this pull request:
+-  
+- 
+- 
+
+### Checklist
+- [ ] Check the commit's or even all commits' message styles matches our requested structure.
+- [ ] Check your code additions will fail neither code linting checks nor unit test.
+
+```
+
+## 2.3 Create a template repository
+
+1. Navigate to the `Settings > General` page of your repository
+2. Select `Template repository` checkbox
+3. Navigate to your repository list and click `New repository`
+4. The `repository template` list should contain your new repository template
+5. _(Optional)_ Create a new repository from one of the templates
+6. _(Optional)_ Navigate to your repository template and click on the `Use this template` button
+
diff --git a/labs/lab05.md b/labs/lab05.md
@@ -0,0 +1,69 @@
+# 5 - GitHub API - REST API & GraphQL API
+In this lab you will create a workflow that calls GitHub APIs using REST API and GraphQL API.
+> Duration: 15-20 minutes
+
+References:
+- [GitHub GraphQL API - GitHub Docs](https://docs.github.com/en/graphql)
+- [GitHub REST API - GitHub Docs](https://docs.github.com/en/rest)
+- [Migrating from REST to GraphQL - GitHub Docs](https://docs.github.com/en/graphql/guides/migrating-from-rest-to-graphql)
+- [actions/github-script](https://github.com/actions/github-script)
+- [octokit/graphql-action](https://github.com/octokit/graphql-action)
+- [See octokit/rest.js for the API client documentation](https://octokit.github.io/rest.js/v18)
+
+## 5.1 Develop a GitHub Action workflow that calls REST APIs
+
+1. Open the workflow file [use-github-apis.yml](/.github/workflows/use-github-apis.yml)
+2. Edit the file and copy the following YAML content at the end of the `rest-api-create-and-close-issue` job:
+```YAML
+      - uses: actions/github-script@v6
+        id: close-issue
+        with:
+          github-token: ${{secrets.GITHUB_TOKEN}}
+          script: |
+            const result = await github.rest.issues.update({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: ${{fromJSON(steps.create-issue.outputs.result).number}},
+              state: 'closed'
+            })            
+            console.log(result)
+```
+3. Commit the changes into the `main` branch
+4. Go to `Actions` and see the details of your running workflow
+
+## 5.2 Develop a GitHub Action workflow that calls GraphQL APIs
+
+1. Open the workflow file [use-github-apis.yml](/.github/workflows/use-github-apis.yml)
+2. Edit the file and copy the following YAML content at the end of the file:
+```YAML
+  graphql-api-query-labels:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v6
+        id: labels-result
+        with:
+          script: |
+            const query = `query($owner:String!, $name:String!) {
+              repository(owner:$owner, name:$name){
+                labels (last:100) {
+                  nodes {
+                    name,
+                    color,
+                    issues(last:100) {
+                      nodes {
+                        number
+                      }
+                    }
+                  }
+                }
+              }
+            }`;
+            const variables = {
+              owner: context.repo.owner,
+              name: context.repo.repo
+            }
+            const result = await github.graphql(query, variables)
+            console.log(result.repository.labels.nodes)
+```
+3. Commit the changes into the `main` branch
+4. Go to `Actions` and see the details of your running workflow
