> On Nov 9, 2022, at 01:52, Uwe Schindler <u...@thetaphi.de> wrote:
> 
> Hi Andi,
> 
>> I did that now, and wouldn't have if someone had told me about the branch 
>> change.
> 
> Normally before you push the branch and edit anything, you should do a "git 
> pull" to get latest changes from server. A "git pull" fails with error 
> message if the branch does not exist on server. So normally you would notice 
> the issue. It is exactly like with Subversion, if you update a branch there 
> that no longer exists, you get a 404. The only difference (and that's the 
> pain) on Git: if you push a non-existing branch, it is created on server 
> automatically.
> 
> We changed from master to main long ago, I think at latest when we splitted 
> Lucene/Solr. Sorry for not informing you.

Well, I made a release against 'master' in April of this year and nothing broke 
then.

>>> I will check how to setup branch protection to not allow pushing a master 
>>> branch.
>> 
>> I no longer have a master branch on my system.
> 
> Great!
> 
> No problem, it seems all well again,

Good, thank you for catching and fixing this and sorry for the noise.

Andi..

> 
> Uwe
> 
>> Andi..
>> 
>>> 
>>> Uwe
>>> 
>>> Am 09.11.2022 um 01:42 schrieb Uwe Schindler:
>>>> Hi Andi,
>>>> 
>>>> you pushed the "master" branch to lucene-site Git repo, which was outdated 
>>>> and was no longer existing on server. I deleted it because main AND master 
>>>> cause issues with website build and makes it hard to understand what needs 
>>>> to be changed for website updates. Please push your changes to "main" 
>>>> branch! The problem with duplicate branches is that your push removed some 
>>>> stuff from the website.
>>>> 
>>>> Your last push was yesterday and that caused havoc: it removed our latest 
>>>> releases from web page because you were overwriting it with an old version.
>>>> 
>>>> Please cleanup your local repo and use "main" branch instead. I don't know 
>>>> what changes are now lost by deleting the branch on server. Please add 
>>>> your release of python lucene again on correct branch.
>>>> 
>>>> Uwe
>>>> 
>>>>> Am 28.04.2022 um 02:02 schrieb va...@apache.org:
>>>>>> This is an automated email from the ASF dual-hosted git repository.
>>>>>> 
>>>>>> vajda pushed a change to branch master
>>>>>> in repository https://gitbox.apache.org/repos/asf/lucene-site.git
>>>>>> 
>>>>>> 
>>>>>>        at 038f44716 release 9.1.0
>>>>>> 
>>>>>> This branch includes the following new commits:
>>>>>> 
>>>>>>       new 038f44716 release 9.1.0
>>>>>> 
>>>>>> The 1 revisions listed above as "new" are entirely new to this
>>>>>> repository and will be described in separate emails.  The revisions
>>>>>> listed as "add" were already present in the repository and have only
>>>>>> been added to this reference.
>>>>>> 
>>> -- 
>>> Uwe Schindler
>>> Achterdiek 19, D-28357 Bremen
>>> https://www.thetaphi.de
>>> eMail: u...@thetaphi.de
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>> 
>>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
> 
> -- 
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> https://www.thetaphi.de
> eMail: u...@thetaphi.de
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to