I deleted all "merged" branches.
I'd agree that it's a good custom to push feature branches into forked
local repos, not the master repo (unless it's really necessary).
For the moment, please check branches you created and delete obsolete ones.
https://github.com/apache/lucene-solr/branches/all
On Mon, 19 Oct 2020 at 14:24, Uwe Schindler wrote:
> Nice possibility on top: You can force push as often as you like! ☕藍
>
Up until the point you create a PR. After that, I think it gets confused
and doubles the entries. Unless I messed up one of my PRs even worse than I
thought.
+1 on doing
Nice possibility on top: You can force push as often as you like! ☕藍
Am October 19, 2020 6:18:59 PM UTC schrieb Erick Erickson
:
>+1, this is what I’ve been doing for a while, and it gives me a warm
>fuzzy feeling to know that no mater what, until the final merge into
>the master repo I can’t
+1, this is what I’ve been doing for a while, and it gives me a warm fuzzy
feeling to know that no mater what, until the final merge into the master repo
I can’t inadvertently screw up said master repo….
> On Oct 19, 2020, at 1:53 PM, David Smiley wrote:
>
> +100 to Uwe's total message -- my
+100 to Uwe's total message -- my thoughts exactly. When I first started
using GitHub, I had an SVN mindset and didn't recognize the point of repo
forks. Now I can clearly see that it allows for PRs that don't pollute the
branches in the master repo.
On Mon, Oct 19, 2020 at 1:01 PM Uwe
Hi Tomoko,
IMHO, people should open PRs using a branch on their own GitHub fork. It also
works well when you work together. Any ASF org member on GitHub can
automatically commit and push to private branches of outside users, as GitHub
enforces you to allow pushes from members of the org the PR
Thank you Jan for the pointer.
I read the Infra wiki, and checked the yaml files in several major ASF
repositories (e.g. Hadoop, Flink, Kafka, AIrflow, ...). It looks like there
is no such configuration for the feature.
If it's ok I will delete all branches that have been already merged.
Also I'd
Check the .asf.yml file in our repo and
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
That’s where we control github features… But I cannot see that option.
Jan
> 19. okt. 2020 kl. 16:20 skrev Tomoko Uchida :
>
> Hi,
> it seems there are many active branches that
Hi,
it seems there are many active branches that are already merged into master
via Github PR.
Github has a configuration to automatically delete the branch when a PR is
merged (Settings -> Options -> "Automatically delete head branches") but I
think it is disabled by default.
I cannot change the