blocks|key|93569|text|您也可以使用github+api。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|93570|使用curl的示例|93571|curl+--user+"your_github_username"+\
+++++--request+PATCH+\
+++++--data+'{"title":"newtitle","body":"newbody",...}'+\
+++++https://api.github.com/repos/:owner/:repo/pulls/:number|code-block|syntax|javascript|93572|您可以在github+developer+doc中找到详细的数据列表|93573|示例:更改my+pull+request的名称|93574|curl+--user+"jeremyclement"+\
+++++--request+PATCH+\
+++++--data+'{"title":"allows+the+control+of+files+and+folders+permissions."}'+\
+++++https://api.github.com/repos/Gregwar/Cache/pulls/9|93575|entityMap|0|LINK|mutability|MUTABLE|url|https://api.github.com/|1|http://en.wikipedia.org/wiki/CURL|2|https://developer.github.com/v3/pulls/#update-a-pull-request|3|https://github.com/Gregwar/Cache/pull/9^0|6|A|0|0|2|4|1|0|0|4|K|2|0|5|F|3|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|F|3|G|5|H|7|1C|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1D|8|@]|9|@$A|1E|B|1F|1|1G]]|C|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@$A|1I|B|1J|1|1K]]|C|$]]|$1|O|3|P|5|H|7|1L|8|@]|9|@]|C|$I|J]]|$1|Q|3|-4|5|6|7|1M|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]|10|$5|T|U|V|C|$W|11]]|12|$5|T|U|V|C|$W|13]]]]

<p>You also can use <a href="https://api.github.com" rel="nofollow noreferrer">github api</a>.</p>
<h3>example with <a href="http://en.wikipedia.org/wiki/CURL" rel="nofollow noreferrer">curl</a></h3>
<pre><code>curl --user &quot;your_github_username&quot; \
     --request PATCH \
     --data '{&quot;title&quot;:&quot;newtitle&quot;,&quot;body&quot;:&quot;newbody&quot;,...}' \
     https://api.github.com/repos/:owner/:repo/pulls/:number
</code></pre>
<p>you can find the detailled list of data in <a href="https://developer.github.com/v3/pulls/#update-a-pull-request" rel="nofollow noreferrer">github developer doc</a></p>
<h3>example : change name of <a href="https://github.com/Gregwar/Cache/pull/9" rel="nofollow noreferrer">my pull request</a></h3>
<pre><code>curl --user &quot;jeremyclement&quot; \
     --request PATCH \
     --data '{&quot;title&quot;:&quot;allows the control of files and folders permissions.&quot;}' \
     https://api.github.com/repos/Gregwar/Cache/pulls/9
</code></pre>


blocks|key|310587|text|我在拉取请求中只有一次提交，并且我使用git+commit+--amend来更新它。然后我用git+push+-f做了一个强制推送，所以我修改后的提交替换了原来的提交。拉取请求自动获取新的提交。(它实际上显示了两个提交，但是当我重新加载页面时，旧的提交已经消失了。)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|310588|因此，虽然通常不推荐强制推送，但它对于拉取请求很有用。不推荐这样做，因为如果有人将提交建立在您的基础之上，那么他们将不得不在您的更改之后进行重新基础。但由于没有人应该将他们的工作建立在审查下的拉取请求上，所以在这种情况下应该是相当安全的。|310589|entityMap^0|J|I|1A|B|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

<p>I just had one commit in a pull request, and I used <code>git commit --amend</code> to update it.  I then did a force push with <code>git push -f</code> so my amended commit replaced the original one.  The pull request automatically picked up the new commit.  (It actually showed both commits, but when I reloaded the page the old commit had gone.)</p>

<p>So while a forced push is generally not recommended, it can be useful for pull requests.  It's not recommended because if someone bases a commit on top of yours then they will have to do a rebase after your change.  But since nobody should be basing their work on an under-review pull request, it should be pretty safe in this situation.</p>


blocks|key|310596|text|在创建PR的现有分支上应用您的更改。例如，如果您的分支名称是newFeature，并且您有创建PR以将newFeature合并到develop分支中。在newFeature分支上应用建议的更改，并提交任意数量的内容。一旦您完成了修复建议的评审更改。允许审阅者重新审阅它。一旦批准，您应该能够合并您的公关。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|310597|如果您需要有关git的一般帮助，可以使用SourceTree或其他图形用户界面工具。|310598|entityMap^0|U|A|1F|A|1S|7|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

<p>Apply your changes over top of your existing branch where the PR is created. For example if you branch name is <code>newFeature</code> and you have create PR to merge <code>newFeature</code> into <code>develop</code> branch. Apply the suggested changes on the newFeature branch with as many commits you want. Once you are completed with fixing suggested review changes. Allow the reviewer to re-review it. Once approved you should be able to merge your PR.</p>
<p>You can use SourceTree or some GUI tool if you need help in general with git.</p>


<p>I've opened a pull request to a project. The maintainer has decided to accept it, but told me to modify some contents. </p>

<p>How can I do it? Whether I should keep the commit hash unchanged, how can I do it?</p>


How to modify GitHub pull request?

我打开了一个项目的拉取请求。维护人员决定接受它，但告诉我修改一些内容。我该怎么做呢？我是否应该保持提交散列不变，我该怎么做？

问如何修改GitHub拉流请求？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修改GitHub拉流请求？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修改GitHub拉流请求？
EN