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

Added instruction for ignoring the Gemfile.lock file to prevent unsatisfiable dependencies warning in the creating-a-github-pages-site-with-jekyll page #32352

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

Conversation

revolter
Copy link
Contributor

@revolter revolter commented Apr 2, 2024

Why: Warning prevention

Closes: #32351

What's being changed (if available, include any code snippets, screenshots, or gifs):

  • The existing instructions implicitly make you commit and push the Gemfile.lock file, and this PR fixes this

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

@revolter revolter temporarily deployed to preview-env-32352 April 2, 2024 18:13 — with GitHub Actions Inactive
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Apr 2, 2024
Copy link
Contributor

github-actions bot commented Apr 2, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md fpt
ghec
ghes@ 3.12 3.11 3.10 3.9
fpt
ghec
ghes@ 3.12 3.11 3.10 3.9

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review pages Content related to GitHub Pages and removed triage Do not begin working on this issue until triaged by the team labels Apr 2, 2024
@nguyenalex836
Copy link
Contributor

@revolter Thanks so much for opening a PR! I'll get this triaged for review ✨

@revolter
Copy link
Contributor Author

npm ERR! code E401
npm ERR! 401 Unauthorized - GET https://npm.pkg.github.com/@github%2fcocofix - authentication token not provided
npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-04-03T06_24_50_430Z-debug-0.log
Error: Process completed with exit code 1.

I think that the failing lint job is not actually caused by this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team pages Content related to GitHub Pages waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add instruction for ignoring the Gemfile.lock file to prevent unsatisfiable dependencies warning
2 participants