Git Remote Configuration

Prereq: Make Sure You Have Necessary Remotes Configured

Before submitting pull requests to aria-practices, please be sure your proposed changes are based off the latest content in the w3c/aria-practices repository. In order to update your fork with the latest content, you first need to have the necessary remotes configured.

A "remote" essentially tells git the URLs of the repositories you want to use for fetching and pushing. You need two:

Check If You Need to Configure a Remote

To see the remotes you have configured, open git bash in the directory containing your local copy of aria-practices, and execute the command:

git remote -v

This command lists each configured remote along with its fetch and push URLs.

If the output does not include any remotes with URLs that have "/w3c/" in the path or shows only two lines like:

origin  https://github.com/YourID/aria-practices.git (fetch)
origin  https://github.com/YourID/aria-practices.git (push)

then you need to configure a remote that tells git where to find the upstream w3c/aria-practices repository in the w3c github.com account.

Configure Remote for w3c/aria-practices

If you need to add a remote, assuming you want to name it "w3c", execute the command:

git remote add w3c https://github.com/w3c/aria-practices.git

Now, when you list the remotes, you should see something like:

origin  https://github.com/YourID/aria-practices.git (fetch)
origin  https://github.com/YourID/aria-practices.git (push)
w3c     https://github.com/w3c/aria-practices.git (fetch)
w3c     https://github.com/w3c/aria-practices.git (push)

You now have the configuration necessary for keeping your fork current.