> On Nov 9, 2022, at 01:52, Uwe Schindler 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"
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
On Wed, 9 Nov 2022, Uwe Schindler wrote:
I was able to merge the missing changes into the main branch from production.
It should be uptodate now. There was some hickup with asf.yaml, too, but
should be ok now. Website was rebuilt.
Thank you for fixing this !
Please please make sure to NOT
I was able to merge the missing changes into the main branch from
production. It should be uptodate now. There was some hickup with
asf.yaml, too, but should be ok now. Website was rebuilt.
Please please make sure to NOT push to master branch anymore! Please
switch to main and pull changes
On Tue, 8 Nov 2022, Andi Vajda wrote:
Hi Uwe,
On Wed, 9 Nov 2022, Uwe Schindler wrote:
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
Hi Uwe,
On Wed, 9 Nov 2022, Uwe Schindler wrote:
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
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
