From: "Sean" <spbrogan@outlook.com>
To: devel@edk2.groups.io, mikuback@linux.microsoft.com
Cc: Sean Brogan <sean.brogan@microsoft.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 1/1] .github/dependabot.yml: Enable dependabot
Date: Mon, 14 Nov 2022 16:47:56 -0800 [thread overview]
Message-ID: <BY3PR19MB4900B398DCA730E431A17D19C8049@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20221110134654.422-1-mikuback@linux.microsoft.com>
Reviewed-by: Sean Brogan <sean.brogan@microsoft.com>
On 11/10/2022 5:46 AM, Michael Kubacki wrote:
> From: Michael Kubacki <michael.kubacki@microsoft.com>
>
> Enables dependabot in this repo so we can better alerted when
> dependency updates are available.
>
> This GitHub action will automatically create pull requests and
> summarize the dependency details. Because it is a pull request,
> the CI system will validate the dependency update in the pull
> request.
>
> Configures dependabot for:
>
> 1. PIP module updates
> 2. Submodule updates
> 3. GitHub action updates
>
> The maintainers/reviewers of the .github directory were added as
> pull request reviewers so they can be notified when the pull request
> is available.
>
> Cc: Sean Brogan <sean.brogan@microsoft.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
> ---
>
> Notes:
> An example of the pull requests created by this change
> are available on my edk2 fork:
>
> https://github.com/makubacki/edk2/pulls
>
> .github/dependabot.yml | 45 ++++++++++++++++++++
> 1 file changed, 45 insertions(+)
>
> diff --git a/.github/dependabot.yml b/.github/dependabot.yml
> new file mode 100644
> index 000000000000..7f405721fd3d
> --- /dev/null
> +++ b/.github/dependabot.yml
> @@ -0,0 +1,45 @@
> +## @file
> +# Dependabot configuration file to enable GitHub services for managing and updating
> +# dependencies.
> +#
> +# Copyright (c) Microsoft Corporation.
> +# SPDX-License-Identifier: BSD-2-Clause-Patent
> +#
> +# Please see the documentation for all configuration options:
> +# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
> +##
> +version: 2
> +updates:
> + - package-ecosystem: "pip"
> + directory: "/"
> + schedule:
> + interval: "daily"
> + commit-message:
> + prefix: "pip"
> + reviewers:
> + - "makubacki"
> + - "mdkinney"
> + - "spbrogan"
> +
> + - package-ecosystem: "gitsubmodule"
> + directory: "/"
> + schedule:
> + interval: "daily"
> + commit-message:
> + prefix: "submodule"
> + reviewers:
> + - "makubacki"
> + - "mdkinney"
> + - "spbrogan"
> +
> + - package-ecosystem: "github-actions"
> + directory: "/"
> + schedule:
> + interval: "weekly"
> + day: "monday"
> + commit-message:
> + prefix: "GitHub Action"
> + reviewers:
> + - "makubacki"
> + - "mdkinney"
> + - "spbrogan"
prev parent reply other threads:[~2022-11-15 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 13:46 [PATCH v1 1/1] .github/dependabot.yml: Enable dependabot Michael Kubacki
2022-11-10 16:44 ` [edk2-devel] " Michael D Kinney
2022-11-10 19:52 ` Michael Kubacki
2022-11-10 20:16 ` Michael D Kinney
2022-11-11 15:30 ` Michael Kubacki
2022-11-11 18:44 ` Michael D Kinney
2022-11-11 19:10 ` Michael Kubacki
2022-11-15 0:47 ` Sean [this message]
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=BY3PR19MB4900B398DCA730E431A17D19C8049@BY3PR19MB4900.namprd19.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