There was also an update to the infrastructure-actions/pelican@main action that required a small config change in our repo. Did that and merged main into prod. Hope it is fine now and that your PRs will contain only your own stuff..
Jan > 12. juli 2024 kl. 17:52 skrev Houston Putman <hous...@apache.org>: > > It looks like the build stuff Jan had been working on wasn't merged to > production.... I'd definitely wait for him to do that. > > - Houston > > On Fri, Jul 12, 2024 at 10:27 AM Alessandro Benedetti <a.benede...@sease.io> > wrote: > >> Hi all, >> we've been working with my colleagues on adding external Solr blogs to the >> site and we plan to do this periodically, so that each week more or less a >> new blog is published. >> >> But I am confused about the deployment pipeline: >> >> 1) Pull Request *from*: <custom branch> *to*: main >> That's easy peasy, the review happens and when everyone is happy, merge >> >> Then I'm lost, is it: >> >> 2) Pull Request *from*: main *to*: production >> https://github.com/apache/solr-site/pull/111 >> Trying that I see many differences and not the only blog post I was >> supposed to deploy live. >> >> What am I missing? >> >> Cheers >> -------------------------- >> *Alessandro Benedetti* >> Director @ Sease Ltd. >> *Apache Lucene/Solr Committer* >> *Apache Solr PMC Member* >> >> e-mail: a.benede...@sease.io >> >> >> *Sease* - Information Retrieval Applied >> Consulting | Training | Open Source >> >> Website: Sease.io <http://sease.io/> >> LinkedIn <https://linkedin.com/company/sease-ltd> | Twitter >> <https://twitter.com/seaseltd> | Youtube >> <https://www.youtube.com/channel/UCDx86ZKLYNpI3gzMercM7BQ> | Github >> <https://github.com/seaseltd> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@solr.apache.org For additional commands, e-mail: dev-h...@solr.apache.org
