All right, this should be all done now.

https://thrift.staged.apache.org/
https://thrift.apache.org/

I've pushed all branches to the new repo [1] and it seems the Github Action and 
asf.yml are both working correctly, 

Christopher, thank you once again for working on this. Please take a look and 
let me know if anything is wrong or missing.

Best,
Can

[1] https://github.com/apache/thrift-website

On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote:
> 
> Hi guys,
> 
> thanks for the great move forward! Can you send a link to the page
> as soon as something can be seen? I'm still pretty new to the project
> and might have missed if you sent it already, sorry for that :-(
> 
> All the best, Mario
> 
> 
> On 30.10.20 11:19, Duru Can Celasun wrote:
> > I've created the repo using self-service 
> > https://github.com/apache/thrift-website
> > 
> > Once I get write access (I'm assuming it's automated) I'll push all 3 
> > branches and we can take it from there.
> > 
> > On Thu, 29 Oct 2020, at 20:33, Christopher wrote:
> >> I finished the syntax highlighting, but didn't get to the sitemap...
> >> I'm not sure it's all that important.
> >>
> >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once you
> >> get the official repo created, all three branches should be moved
> >> over, as-is, in order for everything to work smoothly. You may need to
> >> ask INFRA to set the "main" branch as the default branch, though.
> >>
> >> If everything is working correctly, you should see the site at
> >> https://thrift.staged.apache.org ; if that is working correctly, then
> >> you can use the _scripts/publish.sh script to push the staging branch
> >> to the publish branch (see README for explanation), and then you'll be
> >> completely off of CMS and can do whatever you want after that. :)
> >>
> >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun <dcela...@apache.org> 
> >> wrote:
> >>>
> >>> This looks excellent Christopher, thank you for working on this so 
> >>> quickly! I'll see if I can create an official repo tomorrow and we can 
> >>> take it from there.
> >>>
>

Reply via email to