Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Gemfile & Gemfile.lock to reduce vulnerabilities #4

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

wzzanthony
Copy link
Owner

The following vulnerabilities are fixed with an upgrade:

6.create a pull request

Copy link

@github-learning-lab github-learning-lab bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was expecting your file to be named _posts/0000-01-02-wzzanthony.md.

Let's edit this pull request to fix both of these issues.

⌨️ Activity: Fixing your pull request

  1. Click the Files Changed tab in this pull request
  2. Verify that the only file edited is named _posts/0000-01-02-wzzanthony.md.
  3. If the file is improperly named, or not in an improper location, click on the pencil icon found on the right side of the screen to edit it.
  4. Above the contents of the file, select all text in the field that contains the filename and delete it.
  5. Continue pressing your backspace key to also delete any directory names that exist.
  6. Type the proper filename:
    _posts/0000-01-02-wzzanthony.md
  7. Scroll to the bottom and enter a commit message and commit in the Commit Changes section.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.


I'll respond below when I detect a commit on this branch.

Copy link

@github-learning-lab github-learning-lab bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 7: Respond to a review

Your pull request is looking great!

Let’s add some content to your file. Replace line 5 of your file with a quotation or meme and witty caption. Remember: Markdown is supported.

⌨️ Activity: Change your file

  1. Click the Files Changed tab in this pull request
  2. Click on the pencil icon found on the right side of the screen to edit your newly added file
  3. Replace line 5 with something new
  4. Scroll to the bottom and click Commit Changes

I'll respond when I detect a commit on this branch.

Copy link

@github-learning-lab github-learning-lab bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Step 8: Merge your pull request

Nicely done @wzzanthony! ✨

You successfully created a pull request, and it has passed all of the tests. You can now merge your pull request.

⌨️ Activity: Merge the pull request

  1. Click Merge pull request

  2. Click Confirm merge

  3. Once your branch has been merged, you don't need it anymore. Click Delete branch.


I'll respond when this pull request is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants