[
https://issues.apache.org/jira/browse/SOLR-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski updated SOLR-13775:
-----------------------------------
Summary: Update PR template to suggest Githubs: "Allow Edits From
Maintainers" option (was: Update PR template to suggest Github's: "Allow Edits
From Maintainers" option)
> Update PR template to suggest Githubs: "Allow Edits From Maintainers" option
> ----------------------------------------------------------------------------
>
> Key: SOLR-13775
> URL: https://issues.apache.org/jira/browse/SOLR-13775
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: github
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Minor
>
> As discussed recently on the mailing list, Github does have one big downside:
> it's pretty onerous for two people to both contribute code to the same PR.
> PR's typically come from personal-fork's of Solr, owned by an individual. If
> that individual doesn't think to give other collaborators edit-access, then
> they must open secondary-PRs to get their changes the primary PR. These
> secondary PRs must be reviewed, merged etc.
> This makes collaboration much more difficult than it is in the patch world
> for example, where I can (e.g.) help a contributor clean up their formatting
> by just uploading a new patch.
> Unfortunately the best workaround at this point for this in github is to
> prompt those opening PRs to grant access to Solr's upstream committers and
> maintainers. We can do this by linking users to this
> [option|https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork]
> in the "PR checklist" that was added recently.
> Users don't have to provide this access if they don't want. But hopefully
> it'll many collaboration easier in many cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
