Piotr, I have seen you applied this *"sync'ing `asf.yaml` between branches"* practice in `logging-parent` too. I find this new setup
- *confusing* – Previously, say, `asf-site` related configuration was only in the `asf-site` branch. Now it is in multiple branches of which it has no association with. - *requiring more work for changes* – If I need to make a change to `asf-site`, I need to update in several branches. - *prone to causing difficult to solve INFRA issues* – We know INFRA is sensitive to configuration overrides that appear in multiple branches. Hence, I prefer you revert all these changes in all repositories and switch back to *"configuration related to branch X goes to branch X"* practice. On Wed, Dec 27, 2023 at 8:50 AM <pkarw...@apache.org> wrote: > This is an automated email from the ASF dual-hosted git repository. > > pkarwasz pushed a commit to branch asf-staging > in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git > > commit ba7e51dee84af097e3246b84238997bc9173aa84 > Author: Piotr P. Karwasz <piotr.git...@karwasz.org> > AuthorDate: Wed Dec 27 08:49:51 2023 +0100 > > Synchronize `.asf.yaml` between site branches > --- > .asf.yaml | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/.asf.yaml b/.asf.yaml > index 46afaa1..545694d 100644 > --- a/.asf.yaml > +++ b/.asf.yaml > @@ -21,3 +21,8 @@ publish: > profile: ~ > whoami: asf-site > subdir: content/log4j/kotlin > + > +staging: > + profile: ~ > + whoami: asf-staging > + subdir: content/log4j/kotlin > >
