<pre style='margin:0'>
Christopher Nielsen (mascguy) pushed a commit to branch master
in repository macports-guide.
</pre>
<p><a href="https://github.com/macports/macports-guide/commit/d638a637595aac1da8a0e2320484b86389deac3d">https://github.com/macports/macports-guide/commit/d638a637595aac1da8a0e2320484b86389deac3d</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'> new d638a63 guide: clarify section "Updating the Guide", esp GitHub tasks
</span>d638a63 is described below
<span style='display:block; white-space:pre;color:#808000;'>commit d638a637595aac1da8a0e2320484b86389deac3d
</span>Author: Jim DeLaHunt <from+project_by_git@jdlh.com>
AuthorDate: Sat Sep 12 23:06:19 2020 -0700
<span style='display:block; white-space:pre;color:#404040;'> guide: clarify section "Updating the Guide", esp GitHub tasks
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> This adds and rewords throughout the Guide, 7.5.1. "Updating the
</span><span style='display:block; white-space:pre;color:#404040;'> Guide".
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> There were no instructions for what to do on github.com. Added
</span><span style='display:block; white-space:pre;color:#404040;'> steps for forking your own copy of the main repo on GitHub.
</span><span style='display:block; white-space:pre;color:#404040;'> Added instructions to push your local branch to the forked repo.
</span><span style='display:block; white-space:pre;color:#404040;'> Added instructions to create a pull request. This has two cases:
</span><span style='display:block; white-space:pre;color:#404040;'> if GitHub notices the new branch and offers to make a PR, or if
</span><span style='display:block; white-space:pre;color:#404040;'> GitHub doesn't notice, and you have to make the PR manually.
</span><span style='display:block; white-space:pre;color:#404040;'> Added instructions for participating in the PR discussion, and for
</span><span style='display:block; white-space:pre;color:#404040;'> making updates to the PR.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> There were no instructions for the Git tasks on the local cloned
</span><span style='display:block; white-space:pre;color:#404040;'> repo as part of proposing a change. Added instructions to
</span><span style='display:block; white-space:pre;color:#404040;'> checkout master, do git pull to pick up changes from MacPorts
</span><span style='display:block; white-space:pre;color:#404040;'> repo, and to create and checkout a branch. Added guidance on
</span><span style='display:block; white-space:pre;color:#404040;'> branch naming. Added instructions for pushing the branch to
</span><span style='display:block; white-space:pre;color:#404040;'> GitHub.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> Also, copyediting throughout. Added intro paragraphs to the top
</span><span style='display:block; white-space:pre;color:#404040;'> section and to the subsections.
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> The <programlisting>...</programlisting> preserve whitespace, so
</span><span style='display:block; white-space:pre;color:#404040;'> either they need wonky indentation, or comments to give indentation
</span><span style='display:block; white-space:pre;color:#404040;'> without whitespace. This confused me. I added comments throughout,
</span><span style='display:block; white-space:pre;color:#404040;'> with notes to help the next editor figure out what's going on:
</span><span style='display:block; white-space:pre;color:#404040;'>
</span><span style='display:block; white-space:pre;color:#404040;'> <!-- [use comments to make programlisting ignore indents] -->
</span>---
guide/xml/project.xml | 182 +++++++++++++++++++++++++++++++++++++++++++++-----
1 file changed, 167 insertions(+), 15 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/guide/xml/project.xml b/guide/xml/project.xml
</span><span style='display:block; white-space:pre;color:#808080;'>index f906f5d..0b0faef 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/guide/xml/project.xml
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/guide/xml/project.xml
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -1147,14 +1147,57 @@ To use the current port, you must be in a port's directory.</screen>
</span> encouraged to submit a pull request following the steps outlined below.
</para>
<span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ We use a triangular workflow to carry changes from contributors to the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ project. You get the latest guide source code from the main repository
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ on GitHub, updating your own "cloned" copy of the repository on your
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ workstation. You make changes on your workstation, in a Git branch. You
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ push the Git branch with your changes to your "forked" copy of the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ repository in your own GitHub account. Then GitHub helps turn that
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ branch into a "pull request". MacPorts developers can review and
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ discuss the pull request with you, and finally decide whether to
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ accept it. This workflow is described in GitHub's guide,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <link xlink:href="https://guides.github.com/activities/forking/">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <citetitle>Forking Projects</citetitle></link>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> <section xml:id="project.docs.guide.one-time">
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <title>Preparing Changes</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <title>Setting Up the Parts of the Workflow</title>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Follow these one-time steps to set up the parts of the workflow.</para>
</span>
<procedure>
<step>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>$</prompt> <userinput>git clone https://github.com/macports/macports-guide.git</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>With your web browser, log in to GitHub.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Go to this guide's main Git repository at
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <link xlink:href="https://github.com/macports/macports-guide" />.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Fork your own copy of the main guide repository.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Click the <guibutton>Fork</guibutton> button, at the top-right of
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the repository window.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ A dialogue may appear: "Where should we fork macports-guide?"
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Select your GitHub username. A message appears,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ "Forking macports/macports-base. It should only take a few seconds."
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Then GitHub moves you to a page labelled,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ "<replaceable>username</replaceable>/macports-guide, forked from
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ macports/macports-guide".
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ This page shows your "forked" copy of the repository, in your
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ own GitHub account.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>On your workstation's command line, clone a copy of
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the main guide repository. Start in a directory which can contain
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the working directory for your local "clone" copy.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>git clone https://github.com/macports/macports-guide.git</userinput>
</span> <!-- --><prompt>$</prompt> <userinput>cd macports-guide</userinput>
<span style='display:block; white-space:pre;background:#ffe0e0;'>-<!-- --><prompt>$</prompt> <userinput>git remote add <replaceable>username</replaceable> https://github.com/<replaceable>username</replaceable>/macports-guide.git</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --><prompt>$</prompt> <userinput>git remote add <replaceable>username</replaceable> https://github.com/<replaceable>username</replaceable>/macports-guide.git</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span> </step>
<step>
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -1168,40 +1211,149 @@ To use the current port, you must be in a port's directory.</screen>
</span> <section xml:id="project.docs.guide.each-time">
<title>Proposing a Change</title>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <para>For each change you want to make:</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>For each change you want to make, follow these steps through the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ triangular workflow. In general, for one pass through this workflow,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ make only one change or set of related changes, in one area of
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the documentation.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ When changing different things, it is preferable to propose separate
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ pull requests.</para>
</span>
<procedure>
<span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>From your workstation's command line, within your local
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ repository directory, switch to your <literal>master</literal>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ branch. Then, pull the latest contents of the master repository
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ to make your repository current.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>cd macports-guide</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --><prompt>$</prompt> <userinput>git checkout master</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --><prompt>$</prompt> <userinput>git pull origin</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Create a Git branch off the <literal>master</literal> branch
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ to hold your changes. The <replaceable>branch-name</replaceable> is
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ a concise string which describes the effect of your change. Generally,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ use words of ASCII letters and digits, separated by underscore
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <literal>'_'</literal> or dash <literal>'-'</literal>,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ e.g. <userinput>clarify_branch_creation_steps</userinput>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ (See <link xlink:href="https://git-scm.com/docs/git-check-ref-format">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <citetitle>git check-ref-format</citetitle></link> for detailed
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ limitations.)
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ If your change fixes a Trac ticket, include the ticket number in
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the branch name, e.g. <userinput>configure-compiler-60331</userinput>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>git checkout -b <replaceable>branch-name</replaceable></userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> <step>
<para>Make your changes to the file in the
<filename>guide/xml/</filename> directory that corresponds to the
section you want to make changes to.</para>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>$</prompt> <userinput>$EDITOR guide/xml/<replaceable>guide.xml</replaceable></userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>$EDITOR guide/xml/<replaceable>guide.xml</replaceable></userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span> </step>
<step>
<para>Verify your changes are still valid XML.
If the <command>make validate</command> command reports
errors, fix the XML sources until you see no more error
<span style='display:block; white-space:pre;background:#ffe0e0;'>- messages</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ messages.</para>
</span>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>$</prompt> <userinput>make validate</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>make validate</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span> </step>
<step>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <para>Convert the guide to HTML and view the new version in your
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- browser.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Convert the guide to HTML, and proofread the new version in
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ your browser.</para>
</span>
<span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>$</prompt> <userinput>make guide</userinput>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-<prompt>$</prompt> <userinput>open guide/html/index.html</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>make guide</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --><prompt>$</prompt> <userinput>open guide/html/index.html</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span> </step>
<step>
<para>Commit your changes to the local branch and describe your
<span style='display:block; white-space:pre;background:#ffe0e0;'>- changes in the commit message. See also our wiki page <link
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- xlink:href="https://trac.macports.org/wiki/CommitMessages">CommitMessages</link>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- that explains how to write good commit messages.</para>
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- <programlisting><prompt>$</prompt> <userinput>git commit -a</userinput></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ changes in the commit message. See also our wiki page, <link
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ xlink:href="https://trac.macports.org/wiki/CommitMessages">
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <citetitle>CommitMessages</citetitle></link>,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ which explains how to write good commit messages.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>git commit -a</userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Push your local branch to your fork of the guide's repository
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ on GitHub. <replaceable>username</replaceable> is your GitHub
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ user name, under which your fork resides.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <programlisting><!-- [use comments to make programlisting ignore indents]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ --><prompt>$</prompt> <userinput>git push <replaceable>username</replaceable></userinput>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+<!-- --></programlisting>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Next, turn your branch into a "pull request" (PR) on GitHub.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>With your web browser, go to this guide's main Git repository
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ at <link xlink:href="https://github.com/macports/macports-guide" />.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>GitHub will likely show you a message that a branch on your
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ forked repo, with your <replaceable>branch-name</replaceable>, "had
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ recent pushes". There is a green button,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <guibutton>Compare & pull request</guibutton>. Push this button.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>If GitHub does not show you that message, create the pull request
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ yourself. Click on the "Pull requests" tab. Click on the green button,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <guibutton>New pull request</guibutton>. The page changes to say
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ "Compare changes", and there are a pair of buttons,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ "base: master" and "compare: master".
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Click on the "compare: master" button, on the right. A dialogue
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ appears, "Choose a head ref".
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Type your GitHub username, followed by colon <literal>':'</literal>.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ The two buttons become four, with the rightmost button reading "compare:".
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Click on the "compare:" button. The list of your branches appears.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Click on the branch which you want to turn into a pull request.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ A green <guibutton>Create pull request</guibutton> button
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ appears, slightly further down the page. Click on this button.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>A dialogue appears. The first line of your commit message
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ is in the title, and the rest of your commit message is in the body.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ Edit these as necessary, then confirm. Your pull request now
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ appears in the list of pull requests.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Now, monitor your GitHub account for messages.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ MacPorts developers may comments and discussion about your pull
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ request. Respond to comments as necessary.</para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>You may want to modify your proposed change. Modify it by
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ repeating the "make your changes" step above, and all the subsequent
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ steps through pushing your branch to your fork on GitHub.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ GitHub will incorporate changes to your fork into the pull request.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </para>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ </step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <step>
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ <para>Once the MacPorts developers are satisfied with your pull
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ request, they will merge it with the main guide respository.</para>
</span> </step>
</procedure>
</section>
</pre><pre style='margin:0'>
</pre>