git clone --branch @branch @auth_project_urlcd @uri@git_username@@uid-no-reply.drupal.org. See Manage your Git identity for details.
git config user.email "@email"git commit and what you could commit by running git add before running git commit.
git checkout -b [branchname]git statusgit statusgit branch -agit checkout [branchname]Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
git add -ugit commit -m "[issue category] #[issue number] by [comma-separated usernames]: [Short summary of the change]."
+git add .git commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."
git push origin @branchgit checkout -b [description]-[issue-number]
+Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
+git add -Agit commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."git statusgit fetch origingit rebase origin/@branchgit format-patch origin/[version] --stdout > [description]-[issue-number]-[comment-number].patchgit checkout -b 7.x-1.xgit commit -am "Commit message"git push origin 7.x-1.xgit checkout 7.x-1.xgit tag 7.x-1.0git push origin 7.x-1.0git format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patchgit clone --branch @branch @anon_project_urlcd @urigit commit and what you could commit by running git add before running git commit.
git checkout -b [branchname]git statusgit statusgit branch -agit checkout [branchname]Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
+git add -ugit commit -m "[issue category] #[issue number] by [comma-separated usernames]: [Short summary of the change]."git checkout -b [description]-[issue-number]
Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
git pullgit rebase
+git add -Agit commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."git statusgit fetch origingit rebase origin/@branchgit format-patch origin/[version] --stdout > [description]-[issue-number]-[comment-number].patchgit format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patchYou will be prompted to enter your Drupal.org password after the first and last step if you have not uploaded an SSH Key or if your SSH key fails. See Authenticating with Git on @@ -465,6 +471,9 @@ Drupal.org for details.
git remote add origin @auth_project_urlgit push origin masterWhen you've completed these steps, refresh this page for further direction.
+ +Note: You have created a local repository. You will not need to complete the One-Time clone on the next page unless you delete your local repository or set up on a different machine. Then, you'll need to perform the One-time setup, as will co-maintainers.
EOT; return $default; } @@ -485,53 +494,67 @@ EOT; function project_git_instructions_sandbox_maintainer() { $default = <<You will be prompted to enter your Drupal.org password after the first step (and any time you make requests from Drupal.org) if you have not uploaded an SSH key or if your SSH key fails. See Authenticate with Git on Drupal.org for details.
git clone --branch @branch @auth_sandbox_urlgit clone --branch @branch @auth_sandbox_url @project_fullnamecd @project_fullnamegit commit and what you could commit by running git add before running git commit.
git checkout -b [branchname] git statusgit statusgit branch -agit checkout [branchname]Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
git add -ugit add .git commit -m "Message about your changes"Note: When patching in response to an issue from -your issue queue, the format for the commit message takes the form +
Note: When patching in response to an issue from your issue queue, the format for the commit message takes the form of:
git commit -m "[issue category] #[issue number] by
-[comma-separated usernames]: [Short summary of the
-change]."git commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."git diff origin/@branchgit push origin @branchgit checkout -b [branchname]
+Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
+git add .git commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."git fetch origingit rebase origin/@branchgit format-patch origin/[version] --stdout > [description]-[issue-number]-[comment-number].patchgit format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patchgit clone --branch @branch @anon_sandbox_urlcd @uri
+git clone --branch @branch @anon_sandbox_url @project_fullnamecd @project_fullname
git commit and what you could commit by running git add before running git commit.
git checkout -b [branchname]git statusgit statusgit branch -agit checkout [branchname]Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
+git add -ugit commit -m "Message about your changes"git checkout -b [branchname]
Note: When patching in response to an issue from the issue queue, the format for the commit message takes the form of:
+Make your changes. Note the change in syntax for issue-related commit messages. See the Commit messages page for details.
git commit -m "[issue category] #[issue number] by [comma-separated usernames]: [Short summary of the change]."git add .git commit -m "Issue #[issue number] by [comma-separated usernames]: [Short summary of the change]."git fetch origingit rebase origin/@branchgit format-patch origin/[version] --stdout > [description]-[issue-number]-[comment-number].patchgit format-patch origin/@branch --stdout > [description]-[issue-number]-[comment-number].patchYou will be prompted to enter your Drupal.org password after the last step (and any time you make requests from Drupal.org) if you have not uploaded an SSH key or if your SSH key fails. See Authenticate with Git on Drupal.org for details.
mkdir @project_fullnameContributed modules on Drupal.org typically use their project's shortname as the prefix to the module's functions. Sandbox shortnames are numbers, which are not valid function names. If you intend to release your code for Drupal.org someday, choose a prefix that isn't being used on Drupal.org already. There is, unfortunately, no guarantee it will still be available when you're ready to release, but you'll save a step if it is. To check, type http://drupal.org/project/[the_name_you_want].
+ +When you've completed these steps, refresh this page for further direction.
+ +Note: You have created a local repository. You will not need to complete the One-Time clone on the next page unless you delete your local repository or set up on a different machine. Then, you'll need to perform the One-time setup, as will co-maintainers.
EOT; return $default; } @@ -604,7 +636,7 @@ function project_git_instructions_reposiGo make a cup of tea. The repository should be ready before you get back.
Reload the page to try again.
-If this message persists longer than 5 minutes, file an issue in the Git component of the Drupal.org Infrastructure queue. Important: Include a link to the project. During testing, do NOT file an issue in the actual Drupal.org queue.
+
If this message persists longer than 5 minutes, file an issue in the Git component of the Drupal.org Infrastructure queue. Important: Include a link to the project.
EOT;
return $default;
}
@@ -620,7 +652,7 @@ EOT;
function project_git_instructions_clone_url_direction() {
$default = <<