Mentoring Playground Issue - Used only for experimentation and training

Nice to see this playground!

Adding "[ignore]" so reviewers know to skip this issue. This is done according to the special issue titles guidelines → . And I think 'other' is a better fit for component.

ChrisDarke → changed the visibility of the branch 3444906-mentoring-playground-issue to hidden.

ChrisDarke → changed the visibility of the branch 3444906-mentoring-playground-issue to active.

Hello, I'm trying to use this to learn how to fork, merge, contribute. When I go to git.drupalcode.org, the "fork" button is disabled. Is that disabled intentionally? Perhaps because this was meant to be a temporary fork for DrupalCon only?

Hi @rraney - I imagine you haven't confirmed your git.drupalcode.org account? Can you fork other repositories?

Hello Randy - I figured out how to get push access above. I also noticed this provided instructions on how to add and fetch. I'm currently attempting to use DrupalForge. When I run this command, it says I don't have access. git fetch drupal-3444906. Also, I didn't get an email from git.drupalcode.org to confirm the account but there was one saying I've been given access to https://git.drupalcode.org/issue/drupal-3444906. I can't click the button there.

I created an issue fork on a random issue. I also can't click on the button "Fork" but I have access. I was able to add and fetch that one. Currently waiting for that one to load into Drupal Forge.

git@git.drupal.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Good luck, but this isn't the place to discuss it. Maybe folks in the Drupal slack #support can direct you to the right place. You have a problem with your git.drupal.org setup or your use of it. This class of problem is almost always fully confirming the git.drupal.org account or using the correct ssh key, etc.