GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Update: Deprecate the documenting-ruby workflow and refer users to ruby/ruby by olleolleolle · Pull Request #6 · documenting-ruby/documenting-ruby.github.io

Conversation

@olleolleolle

@olleolleolle olleolleolle commented Oct 7, 2017 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

This PR is an update to the Step-by-Step Guide which deprecates the workflow currently described on the website.

In order to avoid contributors have their PRs and issues waiting for review here, change the workflow to go towards ruby/ruby instead.

  • instruct users to clone ruby/ruby instead of documenting-ruby/ruby
  • try to keep the documentation published useful still

See also: documenting-ruby/ruby#82 (comment)

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@olleolleolle
Update: Refer only to ruby/ruby
e1db75c 
  - avoid referring people to this org's repository
  - try to keep the documentation published useful still
davydovanton
davydovanton approved these changes Oct 8, 2017
View reviewed changes

@davydovanton davydovanton left a comment

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

Great, thank you ❤️

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
davydovanton
davydovanton reviewed Oct 8, 2017
View reviewed changes
Comment thread _posts/2011-10-06-step-by-step-guide.markdown Outdated
Clone your new repo:
{% highlight bash %}
git clone [email protected]:YOUR_NAME/ruby.git
git clone [email protected]:ruby/ruby.git

@davydovanton davydovanton Oct 8, 2017

Copy link
Copy Markdown
Member

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

I think, after fork you need to use clone [email protected]:YOUR_NAME/ruby.git WDYT?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions

@olleolleolle olleolleolle Oct 9, 2017

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

A suspicion - that upper case word is a magic replacement constant in Github pages. Is this true?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions

@olleolleolle olleolleolle Oct 9, 2017

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

Oh sorry, I was confused. I’ll amend this instruction text to be complete.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@olleolleolle
step-by-step-guide: Link GitHub Help fork article
a0ac30b 
  - try to explain things
@olleolleolle

olleolleolle commented Oct 9, 2017 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Author

@davydovanton I managed to add some more text; most of it was to make a sentence around the GitHub Help article about Forking.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@olleolleolle olleolleolle changed the title Update: Refer only to ruby/ruby Update: Deprecate the documenting-ruby workflow and refer users to ruby/ruby Oct 9, 2017
@mcmire

mcmire commented Apr 17, 2021 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown

Hi, I was thinking of submitting some documentation updates to Ruby and remembered that this site was still a thing. Is it possible to merge this? I think it could be helpful to people.
weedySeaDragon and dafyddcrosby reacted with thumbs up emoji
All reactions
  • 👍 2 reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@davydovanton davydovanton davydovanton approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@olleolleolle @mcmire @davydovanton
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.