You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@attic.apache.org by hb...@apache.org on 2025/04/14 17:04:05 UTC
(attic) branch publish created (now f2302d2)
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to branch publish
in repository https://gitbox.apache.org/repos/asf/attic.git
at f2302d2 publish asf-site branch
This branch includes the following new commits:
new f2302d2 publish asf-site branch
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.
Re: (attic) branch publish created (now f2302d2)
Posted by sebb <se...@gmail.com>.
There are now 3 branches:
main
asf-site
publish
What is the purpose of the asf-site and publish branches?
On Mon, 14 Apr 2025 at 18:04, <hb...@apache.org> wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> hboutemy pushed a change to branch publish
> in repository https://gitbox.apache.org/repos/asf/attic.git
>
>
> at f2302d2 publish asf-site branch
>
> This branch includes the following new commits:
>
> new f2302d2 publish asf-site branch
>
> 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.
>
>
Re: (attic) 01/01: publish asf-site branch
Posted by Herve Boutemy <hb...@apache.org>.
purpose is activating direct publication from Git branch to TLP server
= https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#deploy
with this in place, w'e'll have a modern classical contribution workflow known by any developer:
- open a PR to main for external contributors, waiting for approval by a maintainer
- build done in GitHub Action
- which publishes to website
for maintainers, with Git, we have the choice of direct main contribution or create a branch, do a PR for team review
I don't want to force PR and review for maintainers: keeping maintainer's responsiblity on choosing if the update can just go (as a typo fix) or is worth a review (as this publication activation) is the right choice for us, IMHO
I saw the other question about branches:
- main is the source branch, the main one
- asf-site is the ASF-wide branch name for site publication
- other branches for PR creation are temporary: after feedback, perhaps we should name them "pr/xxx" to clarify that they are for PR creation (I tried, I can't rename without dropping the PR, I'll do in the future)
we're near a huge step forward for getting new contributions
I hope this will help us attract new helpers
helpers on updating our static site generation tooling will be a key next step: no hurry, but definitively important as even more visible than our source and CI
On 2025/04/14 21:45:46 sebb wrote:
> On Mon, 14 Apr 2025 at 18:04, <hb...@apache.org> wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > hboutemy pushed a commit to branch publish
> > in repository https://gitbox.apache.org/repos/asf/attic.git
> >
> > commit f2302d25e1a9869f99725b950b970df59dd35e44
> > Author: Hervé Boutemy <hb...@apache.org>
> > AuthorDate: Mon Apr 14 19:03:52 2025 +0200
> >
> > publish asf-site branch
> > ---
> > .asf.yaml | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/.asf.yaml b/.asf.yaml
> > index c8381f9..508fe51 100644
> > --- a/.asf.yaml
> > +++ b/.asf.yaml
> > @@ -35,6 +35,9 @@ github:
> > - INFRA
> > - ATTIC
> >
> > +publish:
> > + whoami: asf-site
> > +
>
> What is the purpose of this commit?
>
> > notifications:
> > commits: general@attic.apache.org
> > pullrequests: general@attic.apache.org
> >
>
Re: (attic) 01/01: publish asf-site branch
Posted by sebb <se...@gmail.com>.
On Mon, 14 Apr 2025 at 18:04, <hb...@apache.org> wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> hboutemy pushed a commit to branch publish
> in repository https://gitbox.apache.org/repos/asf/attic.git
>
> commit f2302d25e1a9869f99725b950b970df59dd35e44
> Author: Hervé Boutemy <hb...@apache.org>
> AuthorDate: Mon Apr 14 19:03:52 2025 +0200
>
> publish asf-site branch
> ---
> .asf.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/.asf.yaml b/.asf.yaml
> index c8381f9..508fe51 100644
> --- a/.asf.yaml
> +++ b/.asf.yaml
> @@ -35,6 +35,9 @@ github:
> - INFRA
> - ATTIC
>
> +publish:
> + whoami: asf-site
> +
What is the purpose of this commit?
> notifications:
> commits: general@attic.apache.org
> pullrequests: general@attic.apache.org
>
(attic) 01/01: publish asf-site branch
Posted by hb...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch publish
in repository https://gitbox.apache.org/repos/asf/attic.git
commit f2302d25e1a9869f99725b950b970df59dd35e44
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Apr 14 19:03:52 2025 +0200
publish asf-site branch
---
.asf.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.asf.yaml b/.asf.yaml
index c8381f9..508fe51 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -35,6 +35,9 @@ github:
- INFRA
- ATTIC
+publish:
+ whoami: asf-site
+
notifications:
commits: general@attic.apache.org
pullrequests: general@attic.apache.org