profile
viewpoint

brianamarie/10-git-problems 16

10 Git problems & how to solve them

akopyanGit/github-games 0

A fun way to learn about Git and GitHub

beardofedu/vs-ide 0

Repository for Visual Studio IDE Week Collab

billyyumyum2x2/open-enrollment-classes-introduction-to-github 0

open-enrollment-classes-introduction-to-github created by GitHub Classroom

brianamarie/100-days-of-code 0

Fork this template for the 100 days journal - to keep yourself accountable

brianamarie/13-dec 0

Briana's octocat game and documentation

pull request commentgithubtraining/security-strategy-essentials-template

Bump npm from 6.14.4 to 6.14.6

@hectorsector I don't think that updating npm should break the course, since the only "required" vulnerability is for another package. What do you think?

dependabot[bot]

comment created time in 5 days

pull request commentgithub/training-kit

Bump rack from 2.0.8 to 2.2.3

@dependabot merge

dependabot[bot]

comment created time in 18 days

issue commenteverydeveloper/intermediate-python

Problem in Step 3 :(

Hello @adamd 👋 This has been coming up for multiple users. Would you have a chance to take a look? Thanks!

Ashraf95Nagy

comment created time in 18 days

delete branch githubtraining/introduction-to-github

delete branch : fr-translation

delete time in 19 days

push eventgithubtraining/introduction-to-github

Alain Hélaïli

commit sha 3efacc8638ad003a6e669eca8b6feff5e7593809

first translation session

view details

Alain Hélaïli

commit sha de098b98de87cb0ce634e7942204714506161fa8

More :uk: :point_right: :fr:

view details

Alain Hélaïli

commit sha 782fc84b62c78bf7198c5957d201a14e343efa28

:uk: typos

view details

Alain Hélaïli

commit sha 98cf28a6e30421b7a3688f3d255b541741b343e1

Getting closer to the finish line

view details

Alain Hélaïli

commit sha 461df9ba193d76833c82ac7274a71d8a843950dc

:fr: translation and couple :uk: corrections

view details

Alain Hélaïli

commit sha 8423c54d55ca73610d0d4a4b8068d501e17f451f

Solve conflicts

view details

Alain Hélaïli

commit sha bc376b8b9f592fd185c70462ba07b8956c125259

solve conflicts

view details

Alain Hélaïli

commit sha e10f01dbe5251961dd713502dd1af6ab36d58977

Apply @sophielegrand suggestions

view details

Briana Swift

commit sha 5b30c5e8e9ca62fb31bd4203efc60991cc57b804

Merge pull request #44 from githubtraining/fr-translation French translation 🇫🇷

view details

push time in 19 days

PR merged githubtraining/introduction-to-github

French translation 🇫🇷

This PR recreates the work in https://github.com/githubtraining/introduction-to-github/pull/43 so that we can deploy from this branch and test.

+603 -7

7 comments

21 changed files

hectorsector

pr closed time in 19 days

pull request commentgithubtraining/introduction-to-github

French translation 🇫🇷

This is so awesome!!! Thank you so much @helaili and @SophieLegrand!

I have tested this out (English and French) for the first few steps, and everything looks as expected. 🎉 I am on "comms duty" for the team this week, so I'm going to go ahead and merge, and I'll also keep an eye out on the community forum and Halp in case there are any unexpected issues.

hectorsector

comment created time in 19 days

create barnchbrianamarie/github-slideshow

branch : master

created branch time in 19 days

created repositorybrianamarie/github-slideshow

A robot powered training repository :robot:

created time in 19 days

create barnchbrianamarie/github-slideshow

branch : master

created branch time in 19 days

created repositorybrianamarie/github-slideshow

A robot powered training repository :robot:

created time in 19 days

push eventgithub/training-kit

谭九鼎

commit sha 95d672caed4b7ef81748c2cc2648eb613bcbb515

zh-cn: partially revert #736 and sync with en (#752) * zh-cn: partially revert 736 and sync with en * Update github-git-cheat-sheet.md

view details

push time in 20 days

PR merged github/training-kit

zh-cn: partially revert #736 and sync with en

Before merging, there're some questions:

  1. How to understand commit: a Git object, a snapshot of your entire repository compressed into a SHA

    Is it (a snapshot of your entire repository) compressed into a SHA or a snapshot of (your entire repository compressed into a SHA)?

  2. In https://github.com/github/training-kit/pull/724

    图片

    In fact it is git init that "Turn an existing directory into a Git repository". It is usual but not necessary adding remotes. But it's up to you whether changing it.

+40 -36

3 comments

1 changed file

imba-tjd

pr closed time in 20 days

pull request commentgithub/training-kit

Update Persian translation

I am learning about the PR and github in genral. Just curious as to why this PR is still open. May be @brianamarie can comment. Please excuse if this isn't correct way of seeking help.

Hi @Cloud-Mak! Welcome to GitHub! If you haven't already, I recommend going through the First Day on GitHub Learning Path on Learning Lab. That is a great place to start for new users.

This PR is still open because it hasn't gotten the necessary reviews to be merged. Because this pull request makes changes that are not in English, the team that maintains this repository needs help. Once this pull request gets approved by another user who speaks the target language in this pull request, then we will be able to take a closer look and merge. Does that answer your question?

Goudarz

comment created time in 21 days

pull request commentgithub/training-kit

zh-cn: partially revert #736 and sync with en

Great @imba-tjd! Do you happen to know anyone who could review this? Or maybe @vila89 @rwnfoo - would either of you be comfortable reviewing this PR?

imba-tjd

comment created time in 21 days

pull request commentgithub/training-kit

zh-cn: partially revert #736 and sync with en

Hello @imba-tjd! Thank you for opening this pull request!

  1. Is it (a snapshot of your entire repository) compressed into a SHA or a snapshot of (your entire repository compressed into a SHA)?

Good question! It's the first: (a snapshot of your entire repository) compressed into a SHA

2. In https://github.com/github/training-kit/pull/724 In fact it is git init that "Turn an existing directory into a Git repository". It is usual but not necessary adding remotes. But it's up to you whether changing it.

I see your point. I think it makes sense to address this - I will open an issue to make sure that it gets looked at in the English translation.

imba-tjd

comment created time in a month

issue openedgithub/training-kit

Check that `git init` is clearly defined and formatted

Overview

TL;DR As brought up in https://github.com/github/training-kit/pull/752, git init should be clearly defined and formatted to not be confused with other commands, especially those involving remotes.

Extra Detail

Screenshots

图片

How to Contribute

  • [ ] Comment on this issue if you'd like to work/collaborate on it!
  • [ ] Fork the repository.
  • [ ] Use the GitHub Flow to make changes to your fork. This is a refresher course if you're unsure about how to make a change on GitHub.
  • [ ] Push your changes to your repository.
  • [ ] Submit a Pull Request
    • Base Dropdown: github/training-kit
    • Compare Dropdown: Your fork

Testing Locally

If you'd like to make and test changes locally (and see how they would look if merged), do the following:

  • In your command line:
    • Install Git
    • Install Ruby
    • [ ] Run script/setup
    • [ ] Run script/server.
      • When successful, the script will initiate a local server at http://127.0.0.1:4000/.

Questions?

  • Leave a comment on this issue! Make sure to use @ mentions if you want a specific person's attention!

created time in a month

Pull request review commentgithub/training-kit

zh-cn: improve grammar and add translation

 leadingpath: ../../../ [git-scm.com](https://git-scm.com)  ## 配置工具-对所有本地仓库的用户信息进行配置+##### 对所有本地仓库的用户信息进行配置。

It appears https://github.com/github/training-kit/pull/752 is open to address this 👍 Thank you @imba-tjd!

lynkas

comment created time in a month

pull request commentgithubtraining/continuous-delivery-azure-template

Bump websocket-extensions from 0.1.3 to 0.1.4

cc @lmkeston/@mjcastner for comms duty, and @mattdavis0351 as course author 👀 - I believe this should be no problem to merge, but it may be a good idea to test this branch on a fork (or merge, then test quickly in prod) to make sure it doesn't mess up any expected functional behavior.

dependabot[bot]

comment created time in a month

pull request commentgithubtraining/continuous-delivery-aws-template

Bump websocket-extensions from 0.1.3 to 0.1.4

@lmkeston/@mjcastner for comms duty, and @mattdavis0351 as course author 👀 - I believe this should be no problem to merge, but it may be a good idea to test this branch on a fork (or merge, then test quickly in prod) to make sure it doesn't mess up any expected functional behavior.

dependabot[bot]

comment created time in a month

pull request commentgithubtraining/using-github-actions-for-ci-template

Bump websocket-extensions from 0.1.3 to 0.1.4

@lmkeston/@mjcastner for comms duty, and @mattdavis0351 as course author 👀 - I believe this should be no problem to merge, but it may be a good idea to test this branch on a fork (or merge, then test quickly in prod) to make sure it doesn't mess up any expected functional behavior.

dependabot[bot]

comment created time in a month

pull request commentgithubtraining/react-solution

Bump websocket-extensions from 0.1.3 to 0.1.4

@dependabot merge

dependabot[bot]

comment created time in a month

PR closed brianamarie/github-actions-continuous-delivery

Bump websocket-extensions from 0.1.3 to 0.1.4 dependencies

Bumps websocket-extensions from 0.1.3 to 0.1.4. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/faye/websocket-extensions-node/blob/master/CHANGELOG.md">websocket-extensions's changelog</a>.</em></p> <blockquote> <h3>0.1.4 / 2020-06-02</h3> <ul> <li>Remove a ReDoS vulnerability in the header parser (CVE-2020-7662, reported by Robert McLaughlin)</li> <li>Change license from MIT to Apache 2.0</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/faye/websocket-extensions-node/commit/8efd0cd6e35faf9bb9cb08759be1e27082177d43"><code>8efd0cd</code></a> Bump version to 0.1.4</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/3dad4ad44a8c5f74d4f8f4efd3f9d6e0b5df3051"><code>3dad4ad</code></a> Remove ReDoS vulnerability in the Sec-WebSocket-Extensions header parser</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/4a76c75efb1c5d6a2f60550e9501757458d19533"><code>4a76c75</code></a> Add Node versions 13 and 14 on Travis</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/44a677a9c0631daed0b0f4a4b68c095b624183b8"><code>44a677a</code></a> Formatting change: {...} should have spaces inside the braces</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/f6c50aba0c20ff45b0f87cea33babec1217ec3f5"><code>f6c50ab</code></a> Let npm reformat package.json</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/2d211f3705d52d9efb4f01daf5a253adf828592e"><code>2d211f3</code></a> Change markdown formatting of docs.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/0b620834cc1e1f2eace1d55ab17f71d90d88271d"><code>0b62083</code></a> Update Travis target versions.</li> <li><a href="https://github.com/faye/websocket-extensions-node/commit/729a4653073fa8dd020561113513bfa2e2119415"><code>729a465</code></a> Switch license to Apache 2.0.</li> <li>See full diff in <a href="https://github.com/faye/websocket-extensions-node/compare/0.1.3...0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+33 -14

0 comment

1 changed file

dependabot[bot]

pr closed time in a month

pull request commentgithubtraining/react-template

Bump websocket-extensions from 0.1.3 to 0.1.4

@dependabot merge

dependabot[bot]

comment created time in a month

issue closedgithub/training-kit

Okay

Overview

TL;DR <One to two sentence description of the issue you are encountering or trying to solve.>

Extra Detail

Screenshots

<If bug fix, please upload images of the error to better showcase the problem.>

Reasoning

<If new idea or direction, please create a checklist of proposed ideas or next steps. Example.>

How to Contribute

  • [x] Comment on this issue if you'd like to work/collaborate on it!
  • [x] Fork the repository.
  • [x] Use the GitHub Flow to make changes to your fork. This is a refresher course if you're unsure about how to make a change on GitHub.
  • [x] Push your changes to your repository.
  • [x] Submit a Pull Request
    • Base Dropdown: github/training-kit
    • Compare Dropdown: Your fork

Testing Locally

If you'd like to make and test changes locally (and see how they would look if merged), do the following:

  • In your command line:
    • Install Git
    • Install Ruby
    • [x] Run script/setup
    • [x] Run script/server.
      • When successful, the script will initiate a local server at http://127.0.0.1:4000/.

Questions?

  • Leave a comment on this issue! Make sure to use @ mentions if you want a specific person's attention!

closed time in a month

GearHead001

issue closedgithub/training-kit

fff

Overview

TL;DR <One to two sentence description of the issue you are encountering or trying to solve.>

Extra Detail

Screenshots

<If bug fix, please upload images of the error to better showcase the problem.>

Reasoning

<If new idea or direction, please create a checklist of proposed ideas or next steps. Example.>

How to Contribute

  • [x] Comment on this issue if you'd like to work/collaborate on it!
  • [ ] Fork the repository.
  • [x] Use the GitHub Flow to make changes to your fork. This is a refresher course if you're unsure about how to make a change on GitHub.
  • [ ] Push your changes to your repository.
  • [x] Submit a Pull Request
    • Base Dropdown: github/training-kit
    • Compare Dropdown: Your fork

Testing Locally

If you'd like to make and test changes locally (and see how they would look if merged), do the following:

  • In your command line:
    • Install Git
    • Install Ruby
    • [x] Run script/setup
    • [x] Run script/server.
      • When successful, the script will initiate a local server at http://127.0.0.1:4000/.

Questions?

  • Leave a comment on this issue! Make sure to use @ mentions if you want a specific person's attention!

closed time in a month

baxbany139

pull request commentgithub/training-kit

Bump activesupport from 6.0.2.1 to 6.0.3.1

cc @lmkeston because I believe you are on comms duty - it looks like there are some problems with the pages build that I'm not sure are related to this update. If you don't have time to investigate this week, please let me know and I'll try to help or find folks that can. 😊

dependabot[bot]

comment created time in a month

pull request commentgithub/training-kit

Bump activesupport from 6.0.2.1 to 6.0.3.1

@mattdavis0351, it looks like you are currently on comms duty. Please let me know if you won't be able to get to this PR this week and I will take a closer look at it to get it merged. 😊

dependabot[bot]

comment created time in 2 months

pull request commentgithubtraining/introduction-to-github

French translation 🇫🇷

I did @brianamarie but as mentioned on Slack I need push access to be able to commit it back.

Ah - I'm so sorry I missed that before. I've opened a PR with entitlements that should unblock you once it's merged. 😄

hectorsector

comment created time in 2 months

pull request commentgithubtraining/introduction-to-github

French translation 🇫🇷

Friendly bump on this @helaili - have you had a chance to look over @SophieLegrand's review?

hectorsector

comment created time in 2 months

push eventgithub/training-kit

Abhijeet Singh

commit sha 1515b1a90115929bcd8df9652e1021848e80a914

Update github-git-cheat-sheet.md (#747) Fix terminal command for git commit

view details

push time in 2 months

PR merged github/training-kit

Update github-git-cheat-sheet.md

Fix terminal command for git commit

Overview

TL;DR Erroneous git commit command at the git cheat sheet page. Whitespace should be present between the -m flag and the commit message.

Closes #746

+1 -1

1 comment

1 changed file

cseas

pr closed time in 2 months

issue closedgithub/training-kit

Mistake in command mentioned for git commit

Overview

TL;DR Whitespace should be present between the -m flag and the commit message in the git commit command mentioned in git cheat sheet.

closed time in 2 months

cseas

pull request commentgithub/training-kit

Update github-git-cheat-sheet.md

Thank you for submitting this fix, @cseas!

cseas

comment created time in 2 months

delete branch brianamarie/github-slideshow

delete branch : my-slide

delete time in 2 months

push eventbrianamarie/github-slideshow

Briana Swift

commit sha 4e4f973315705c929fc8cd8c5d618f6db5c4f22a

create new post

view details

Briana Swift

commit sha 9233dea5d56df9f018d4b2dd723ce1293a489ed7

Update 0000-01-02-brianamarie.md

view details

Briana Swift

commit sha f52bcb4d02ac7d5931b245edddb0a630b41a7c51

Merge pull request #3 from brianamarie/my-slide Add brianamarie's file

view details

push time in 2 months

PR merged brianamarie/github-slideshow

Add brianamarie's file

OH yeah baby

+7 -0

0 comment

1 changed file

brianamarie

pr closed time in 2 months

push eventbrianamarie/github-slideshow

Briana Swift

commit sha 9233dea5d56df9f018d4b2dd723ce1293a489ed7

Update 0000-01-02-brianamarie.md

view details

push time in 2 months

PR opened brianamarie/github-slideshow

Add brianamarie's file

OH yeah baby

+6 -0

0 comment

1 changed file

pr created time in 2 months

push eventbrianamarie/github-slideshow

Briana Swift

commit sha 4e4f973315705c929fc8cd8c5d618f6db5c4f22a

create new post

view details

push time in 2 months

create barnchbrianamarie/github-slideshow

branch : my-slide

created branch time in 2 months

issue closedbrianamarie/github-slideshow

Getting Started with GitHub

:wave: Welcome to GitHub Learning Lab's "Introduction to GitHub"

To get started, I’ll guide you through some important first steps in coding and collaborating on GitHub.

:point_down: This arrow means you can expand the window! Click on them throughout the course to find more information. <details><summary>What is GitHub?</summary> <hr>

What is GitHub?

I'm glad you asked! Many people come to GitHub because they want to contribute to open source <sup>:book:</sup> projects, or they're invited by teammates or classmates who use it for their projects. Why do people use GitHub for these projects?

At its heart, GitHub is a collaboration platform.

From software to legal documents, you can count on GitHub to help you do your best work with the collaboration and security tools your team needs. With GitHub, you can keep projects completely private, invite the world to collaborate, and streamline every step of your project.

GitHub is also a powerful version control tool.

GitHub uses Git <sup>:book:</sup>, the most popular open source version control software, to track every contribution and contributor <sup>:book:</sup> to your project--so you know exactly where every line of code came from.

GitHub helps people do much more.

GitHub is used to build some of the most advanced technologies in the world. Whether you're visualizing data or building a new game, there's a whole community and set of tools on GitHub that can get you to the next step. This course starts with the basics, but we'll dig into the rest later!

:tv: Video: What is GitHub? <hr> </details><br>

<details><summary>Exploring a GitHub repository</summary> <hr>

Exploring a GitHub repository

:tv: Video: Exploring a repository

More features

The video covered some of the most commonly-used features. Here are a few other items you can find in GitHub repositories:

  • Project boards: Create Kanban-style task tracking board within GitHub
  • Wiki: Create and store relevant project documentation
  • Insights: View a drop-down menu that contains links to analytics tools for your repository including:
    • Pulse: Find information about the work that has been completed and the work that’s in-progress in this project dashboard
    • Graphs: Graphs provide a more granular view of the repository activity including who contributed to the repository, who forked it, and when they completed the work

Special Files

In the video you learned about a special file called the README.md. Here are a few other special files you can add to your repositories:

  • CONTRIBUTING.md: The CONTRIBUTING.md is used to describe the process for contributing to the repository. A link to the CONTRIBUTING.md file is shown anytime someone creates a new issue or pull request.
  • ISSUE_TEMPLATE.md: The ISSUE_TEMPLATE.md is another file you can use to pre-populate the body of an issue. For example, if you always need the same types of information for bug reports, include it in the issue template, and every new issue will be opened with your recommended starter text.

<hr> </details>

Using issues

This is an issue <sup>:book:</sup>: a place where you can have conversations about bugs in your code, code review, and just about anything else.

Issue titles are like email subject lines. They tell your collaborators what the issue is about at a glance. For example, the title of this issue is Getting Started with GitHub.

<details><summary>Using GitHub Issues</summary>

Using GitHub issues

Issues are used to discuss ideas, enhancements, tasks, and bugs. They make collaboration easier by:

  • Providing everyone (even future team members) with the complete story in one place
  • Allowing you to cross-link to other issues and pull requests <sup>:book:</sup>
  • Creating a single, comprehensive record of how and why you made certain decisions
  • Allowing you to easily pull the right people and teams into a conversation with @-mentions

:tv: Video: Using issues

<hr> </details>

<details><summary>Managing notifications</summary> <hr>

Managing notifications

:tv: Video: Watching, notifications, stars, and explore

Once you've commented on an issue or pull request, you'll start receiving email notifications when there's activity in the thread.

How to silence or unmute specific conversations

  1. Go to the issue or pull request
  2. Under "Notifications", click the Unsubscribe button on the right to silence notifications or Subscribe to unmute them

You'll see a short description that explains your current notification status.

How to customize notifications in Settings

  1. Click your profile icon
  2. Click Settings
  3. Click Notifications from the menu on the left and adjust your notification preferences

Repository notification options

  • Watch: You'll receive a notification when a new issue, pull request or comment is posted, and when an issue is closed or a pull request is merged
  • Not watching: You'll no longer receive notifications unless you're @-mentioned
  • Ignore: You'll no longer receive any notifications from the repository

How to review notifications for the repositories you're watching

  1. Click your profile icon
  2. Click Settings
  3. Click Notification from the menu on the left
  4. Click on the repositories you’re watching link
  5. Select the Watching tab
  6. Click the Unwatch button to disable notifications, or Watch to enable them

<hr> </details>

<hr> <h3 align="center">Keep reading below to find your first task</h3>

closed time in 2 months

github-learning-lab[bot]

create barnchbrianamarie/github-slideshow

branch : master

created branch time in 2 months

created repositorybrianamarie/github-slideshow

A robot powered training repository :robot:

created time in 2 months

pull request commentgithubtraining/react-course

Fixing some typos

👍 This looks good to me @crichID! Please let me know if you'd like me to merge, but I will hold off for now in case you want to show the merge process in a future livestream 😊

cynthiarich

comment created time in 2 months

pull request commenttasb/github-actions-for-ci

CI for Node

Hi @tasb! I saw your message in the community forum. I'm not sure why the course got stuck, but I've manually moved you on to the next step. Here are the instructions that the bot would have posted. You should be on track to finish the course from here, but if you have any other problems, please let me know. You can find the instructions for your next step in #4.

tasb

comment created time in 2 months

issue openedtasb/github-actions-for-ci

Next step:

Hi @tasb! I saw your message in the community forum. I'm not sure why the course got stuck, but I've manually moved you on to the next step. Here are the instructions that the bot would have posted. You should be on track to finish the course from here, but if you have any other problems, please let me know.

Custom workflow

Now that we've learned how to quickly set up CI, let's try a more realistic use case.

Our fictional team has a custom workflow that goes beyond the template we've used so far. We would like the following features:

  • test against multiple targets so that we know if our supported operating systems and Node.js versions are working
  • dedicated test job so that we can separate out build from test details
  • access to build artifacts so that we can deploy them to a target environment
  • branch protections so that the master branch can't be deleted or inadvertently broken
  • required reviews so that any pull requests are double checked by teammates
  • obvious approvals so we can merge quickly and potentially automate merges and deployments

Step 7: Create a custom GitHub Actions workflow

Can GitHub Actions support this workflow? Let's find out. We'll tackle some of the changes to the existing workflow file first.

:keyboard: Activity: Edit the existing workflow with new build targets

  1. Edit your existing workflow file in a new branch
  2. In that file, target versions 8.x and 10.x of Node, only
  3. Open a new pull request titled Improve CI for your change.

I'll respond when you open the pull request.

created time in 2 months

pull request commentgithubtraining/using-github-actions-for-ci

Minor typo in ubuntu container image name

cc @mattdavis0351 👀

MAHDTech

comment created time in 2 months

issue commentgithubtraining/continuous-delivery-azure

Course Feedback from MSFT

cc @githubtraining/programs @mattdavis0351 👀

a-a-ron

comment created time in 2 months

pull request commentgithubtraining/write-javascript-actions

Changed github.Github to github.GitHub

@mattdavis0351 🚢 :shipit:

markharrison

comment created time in 2 months

pull request commentgithubtraining/write-javascript-actions

Changed github.Github to github.GitHub

Yep, you did everything correctly @markharrison! That note was for @mattdavis0351, I'm sorry for the confusion. 😊

markharrison

comment created time in 2 months

pull request commentgithubtraining/write-javascript-actions

Changed github.Github to github.GitHub

@markharrison, thank you for submitting this pull request! @mattdavis0351, would you have bandwidth to review? If you'd like to deploy the changes, you will need to merge this into a branch on this repository instead of a fork, but since it's only text, that may not be necessary. 👍

markharrison

comment created time in 2 months

delete branch githubtraining/write-javascript-actions

delete branch : community-contribution

delete time in 3 months

create barnchgithubtraining/write-javascript-actions

branch : community-contribution

created branch time in 3 months

PR closed github/training-kit

New job

nashsu.typeform.com

Overview

TL;DR <One to two sentence description of the issue you are encountering or trying to solve.>

<Link to related issue. Type closes #RELATEDISSUENUMBER to establish a link.>

Questions

<If relevant, write a list of questions that you would like to discuss related to the changes that you have made.>

Next Steps

<If incomplete, create a task list of items that are still being worked on within the Pull Request.>

Review

<If complete, or ready for :eyes:, use @mentions for quick questions, specific feedback, and progress updates.>

+1 -0

0 comment

1 changed file

foofaa222

pr closed time in 3 months

pull request commentgithubtraining/security-template

Bump debug from 2.6.8 to 3.2.6

@dependabot ignore this major version

dependabot[bot]

comment created time in 3 months

PR closed githubtraining/security-template

Bump debug from 2.6.8 to 3.2.6 dependencies

Bumps debug from 2.6.8 to 3.2.6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/visionmedia/debug/releases">debug's releases</a>.</em></p> <blockquote> <h2>3.2.6</h2> <p>This backport fixes a 4x performance regression when debug is disabled.</p> <h1>Patches</h1> <ul> <li>fix: performance issue (f312a8903a3928c43ff1388828d85f4f8407553d) (<a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/625">#625</a>)</li> </ul> <h2>3.2.5</h2> <p>This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.</p> <p>It is a backport of the <code>4.0.1</code> release.</p> <h3>Patches</h3> <ul> <li>fix browserify and supply alternative unpkg entry point (closes <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/606">#606</a>): cc5f1463d1c975bcef0b3172b2527ca204ec474d</li> </ul> <h2>3.2.4</h2> <blockquote> <p><strong>3.2.4 is DEPRECATED.</strong> See <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/603#issuecomment-420237335">visionmedia/debug#603</a> for details.</p> </blockquote> <p>This released fixed the missing <code>files</code> entry in <code>package.json</code>, mitigating the faulty <code>3.2.3</code> release.</p> <h2>3.2.3</h2> <blockquote> <p><strong>3.2.3 is DEPRECATED.</strong> See <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/603#issuecomment-420237335">visionmedia/debug#603</a> for details.</p> </blockquote> <p>This release mitigated the breaking changes introduced in <code>3.2.0</code> where <code>./node.js</code> was removed, breaking a very select few users on older releases of <code>babel-core</code>, as well as users that used an undocumented <code>require('debug/node')</code>.</p> <p><code>./node.js</code> was temporarily added to the repository at this time; however, this release failed to include <code>node.js</code> in the <code>files</code> key in <code>package.json</code> and thus didn't fix the issue. <code>3.2.4</code> rectified this issue.</p> <h2>3.2.2</h2> <blockquote> <p><strong>3.2.2 is DEPRECATED.</strong> See <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/603#issuecomment-420237335">visionmedia/debug#603</a> for details.</p> </blockquote> <p>This release mitigated the breaking changes introduced in <code>3.2.0</code> where ES6 features were being used on users of Node 4, causing crashes upon inclusion.</p> <p>It employed a temporary Babel pass on the entire codebase in lieu of a hard reversion (so this version is, effectively, a backport of the fixes and features ultimately introduced in <code>4.0.0</code>).</p> <h2>3.2.1</h2> <blockquote> <p><strong>3.2.1 is DEPRECATED.</strong> See <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/603#issuecomment-420237335">visionmedia/debug#603</a> for details.</p> </blockquote> <p>This release, along with <code>3.2.0</code>, were subsequently released together as <code>4.0.0</code> (a major bump). You can review the complete changes <a href="https://github.com/visionmedia/debug/releases/tag/4.0.0">in that release's details</a>.</p> <hr /> <p>A quick hotfix to address Browser builds - <code>debug</code> is now compiled down to IE8-compatible code via Babel upon release.</p> <p>CDNs that honor the <code>"browser":</code> key in <code>package.json</code> should now reflect these changes (previously, they would serve the non-bundled ES6 version).</p> <h3>Patches</h3> <ul> <li>use babel-ified distributed source for browsers: b3f8f8e683915ef4fae3a77cbcebc6c410e65a8c</li> </ul> <h2>3.2.0</h2> </tr></table> ... (truncated) </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/visionmedia/debug/commit/a7a17c9955460435592de2a4d3c722e9b32047a8"><code>a7a17c9</code></a> 3.2.6</li> <li><a href="https://github.com/visionmedia/debug/commit/f312a8903a3928c43ff1388828d85f4f8407553d"><code>f312a89</code></a> fix: performance issue</li> <li><a href="https://github.com/visionmedia/debug/commit/9a6d8c20a8b92f7df1f10f343c8238760ec4902f"><code>9a6d8c2</code></a> 3.2.5</li> <li><a href="https://github.com/visionmedia/debug/commit/cc5f1463d1c975bcef0b3172b2527ca204ec474d"><code>cc5f146</code></a> fix browserify and supply alternative unpkg entry point (closes <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/606">#606</a>)</li> <li><a href="https://github.com/visionmedia/debug/commit/78741cceaa01780ad2b4ba859e65ad4c9f52d65a"><code>78741cc</code></a> 3.2.4</li> <li><a href="https://github.com/visionmedia/debug/commit/700a01074456ac42922392c7f327b2d7dfe23dc8"><code>700a010</code></a> re-introduce node.js (root file) (ref <a href="https://github-redirect.dependabot.com/visionmedia/debug/issues/603">#603</a>)</li> <li><a href="https://github.com/visionmedia/debug/commit/622e5798cbe1b9b48930435f2960d6c2f4684300"><code>622e579</code></a> 3.2.2</li> <li><a href="https://github.com/visionmedia/debug/commit/84e41d52acfdaa00ac724277f8c73a550be6916d"><code>84e41d5</code></a> 3.2.1</li> <li><a href="https://github.com/visionmedia/debug/commit/b3f8f8e683915ef4fae3a77cbcebc6c410e65a8c"><code>b3f8f8e</code></a> use babel-ified distributed source for browsers</li> <li><a href="https://github.com/visionmedia/debug/commit/dec4b159ddf63915c94cd9d8421ad11cd06f0e76"><code>dec4b15</code></a> 3.2.0</li> <li>Additional commits viewable in <a href="https://github.com/visionmedia/debug/compare/2.6.8...3.2.6">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~qix">qix</a>, a new releaser for debug since your current version.</p> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

1 comment

1 changed file

dependabot[bot]

pr closed time in 3 months

pull request commentgithubtraining/security-template

Bump debug from 2.6.8 to 3.2.6

NOT merging - this vulnerability is intentional as a part of the course.

dependabot[bot]

comment created time in 3 months

Pull request review commentgithubtraining/write-github-script

Help learner when workflows don't run

 steps:            Like before, now we have to wait for the workflow to run so that we can see the results.   +          <details>+            <summary>Workflow not running? Click here for some troubleshooting.</summary>++          Try the following troubleshooting steps:+          1. Click on the [Actions tab]({{ store.actionsUrl }}) to see the status of your workflow run. See [Managing a workflow run](https://help.github.com/en/actions/configuring-and-managing-workflows/managing-a-workflow-run) on GitHub Help for more information.+          1. Edit your [workflow file]( {{ store.workflowEditUrl }}) and look for errors in the linter built into the browser.+          1. Look for the [workflow trigger](https://help.github.com/en/actions/reference/events-that-trigger-workflows) and ensure you are performing an action that triggers that workflow.

Yay! Unsolicited feedback from me, let's ship to learn!

hectorsector

comment created time in 3 months

more