From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"rebecca@bsdio.com" <rebecca@bsdio.com>,
"mhaeuser@posteo.de" <mhaeuser@posteo.de>,
Gerd Hoffmann <kraxel@redhat.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
Date: Fri, 17 Mar 2023 15:37:16 +0000 [thread overview]
Message-ID: <CO1PR11MB49294F2D60A256DFA097FC95D2BD9@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <42a4d0ce-8dea-9924-acb4-59bbc0a335fe@bsdio.com>
I believe the policies for GitHub Actions artifacts and GitHub PR data retention
are different. Max 90 days for GitHub Actions for public repos:
https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Rebecca Cran
> Sent: Friday, March 17, 2023 7:20 AM
> To: devel@edk2.groups.io; mhaeuser@posteo.de; Gerd Hoffmann <kraxel@redhat.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>
> Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
>
> On 3/17/23 8:08 AM, Marvin Häuser wrote:
> >> On 17. Mar 2023, at 14:44, Gerd Hoffmann <kraxel@redhat.com> wrote:
> >>
> >> Yes, this. For active PRs this usually isn't much of a problem. But
> >> try come back after a few months, or even a few years (see Rebecca
> >> trying to lookup context for a 2016 commit in the archives).
> > I also didn’t find anything in the GutHub docs regarding guarantees for archival. Disgusting.
>
> There's a PR from npm cli from 2018 that still appears to have all data
> about it: https://github.com/npm/cli/pull/1
>
> But, in other places there do seem to be concerns about data retention,
> for example
> https://github.com/tianocore-docs/edk2-VfrSpecification/actions is empty
> and almost certainly had a run in November 2020. I don't know if that's
> something we configured, or if it deletes history for GitHub Actions
> after a few years.
>
>
> --
>
> Rebecca Cran
>
>
>
>
>
next prev parent reply other threads:[~2023-03-17 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 12:32 [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label Marvin Häuser
2023-03-17 12:57 ` Rebecca Cran
2023-03-17 13:44 ` Gerd Hoffmann
2023-03-17 14:08 ` Marvin Häuser
2023-03-17 14:20 ` Rebecca Cran
2023-03-17 15:37 ` Michael D Kinney [this message]
2023-03-17 14:22 ` Rebecca Cran
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 20:02 Michael D Kinney
2023-03-15 22:24 ` [edk2-devel] " Marvin Häuser
2023-03-15 22:34 ` Michael D Kinney
2023-03-16 19:54 ` Marvin Häuser
2023-03-16 19:59 ` Rebecca Cran
2023-03-17 9:33 ` Gerd Hoffmann
2023-03-17 10:36 ` Rebecca Cran
2023-03-17 10:48 ` Rebecca Cran
[not found] ` <174D2F2BAAB7643C.10271@groups.io>
2023-03-17 10:57 ` Rebecca Cran
2023-03-17 15:27 ` Michael D Kinney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO1PR11MB49294F2D60A256DFA097FC95D2BD9@CO1PR11MB4929.namprd11.prod.outlook.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox