Bot releases are visible (Hide)
Published by github-actions[bot] over 1 year ago
This was previously piloted in mu_devops.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.7.4...v1.8.0
Published by github-actions[bot] over 1 year ago
General release Info: https://github.com/microsoft/mu_devops/releases
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.7.3...v1.7.4
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.7.2...v1.7.3
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.7.1...v1.7.2
Published by github-actions[bot] over 1 year ago
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.7.0...v1.7.1
Published by github-actions[bot] over 1 year ago
https://github.com/tianocore/containers/compare/5800d58..5b8a008
Signed-off-by: Michael Kubacki [email protected]
File sync can cause a large impact on CI resources. This change moves
the trigger to a schedule outside office hours (1AM Pacific Time /
9AM UTC daily) to reduce resource usage during most active periods
of other development.
Schedules dependabot checks for times outside normal Pacific
timezone working hours when most development occurs.
Signed-off-by: Michael Kubacki [email protected]
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Adds a workflow to prune issues and pull requests marked as
"won't fix" (via the label state:wont-fix
).
The workflow is scheduled to run every hour. The minimum event
schedule granularity for GitHub is every 5 minutes.
Signed-off-by: Michael Kubacki [email protected]
Signed-off-by: Michael Kubacki [email protected]
When submitting an issue, the submitter can choose to resolve the
issue or request someone else be assigned to resolve it.
This changes makes the submitter the assignee if they choose to
resolve the issue.
Signed-off-by: Michael Kubacki [email protected]
Adds a new selection to issues to request maintainer feedback.
The default is no maintainer feedback is necessary. Opting for
maintainer feedback adds the state:needs-maintainer-feedback
label to the issue.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.6.0...v1.7.0
Published by github-actions[bot] over 1 year ago
Changed the Dashboards for Personal Issues to use github.dev.
Increase the merge and update timeouts to increase likelihood the
operations can occur.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.5.0...v1.6.0
Published by github-actions[bot] almost 2 years ago
The previous value of 5
is the default.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.4.3...v1.5.0
Published by github-actions[bot] almost 2 years ago
Signed-off-by: Michael Kubacki [email protected]
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.4.2...v1.4.3
Published by github-actions[bot] almost 2 years ago
Splitting the workflows provides several benefits:
The reviewers are also dropped from dependabot PRs since the pending
team reviewer is (1) not acted upon (2) can delay PR merging if the
reviewer team has not reviewed the PR.
The version is updated in anticipation of this change. It will be
modified if the expected version changes before this PR is merged.
Signed-off-by: Michael Kubacki [email protected]
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.4.1...v1.4.2
Published by github-actions[bot] almost 2 years ago
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)General release Info: https://github.com/microsoft/mu_devops/releases
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.4.0...v1.4.1
Published by github-actions[bot] almost 2 years ago
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.3.1...v1.4.0
Published by github-actions[bot] almost 2 years ago
This change adds the notice.
Signed-off-by: Michael Kubacki [email protected]
Therefore, those leaf files depended on the main
branch instead
of a mu_devops release tag as the files would be in the main
branch as soon as the PR was merged.
Now that all of the reusable workflows are in a tagged release
(as of the v1.3.0
release), this change sets them to a fixed version
of Mu DevOps as well.
Signed-off-by: Michael Kubacki [email protected]
General release info:
https://github.com/microsoft/mu_devops/releases
Signed-off-by: Michael Kubacki [email protected]
Adds pull request best practices to CONTRIBUTING.md and references this document + pull request best practices in the pull_request_template.md so all contributors are confronted with this guide before they open a pull request rather than afterward by the bot.
TODO:
ensure the relative path to CONTRIBUTING.md in pull_request_template.md is correct since dependent repos have different layout
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.3.0...v1.3.1
Published by github-actions[bot] almost 2 years ago
As automated bots pick up mundane tasks like syncing PIP module
updates, submodules, files, and so on, an increasing number of
pull requests can accumulate that essentially update dependencies
we expect to be updated over time. In most cases, we simply care
that the new update passes CI checks.
This workflow is currently configured to automerge dependabot and
uefibot pull requests.
Files added:
.github/workflows/AutoMerger.yml
- Reusable workflow to auto.sync/workflows/leaf/auto-merge.yml
- Leaf workflow file toSigned-off-by: Michael Kubacki [email protected]
Adds a new workflow and accompanying configuration files that
apply labels to new issues based on options chosen by the submitter
in an issue form.
.github/IssueTriager.yml
- Single reusable workflow to apply.sync/workflows/config/triage-issues/advanced-issue-labeler.yml
-.sync/workflows/leaf/triage-issues.yml
- A leaf workflow that canThis change also enables file syncing of this action to all repos
that issue forms are currently being synced to.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.2.0...v1.3.0
Published by github-actions[bot] almost 2 years ago
Depends on:
https://github.com/microsoft/mu_basecore/pull/199
https://github.com/microsoft/mu_common_intel_min_platform/pull/80
https://github.com/microsoft/mu_plus/pull/118
https://github.com/microsoft/mu_silicon_arm_tiano/pull/32
https://github.com/microsoft/mu_silicon_intel_tiano/pull/29
https://github.com/microsoft/mu_tiano_plus/pull/67
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.1.2...v1.2.0
Published by github-actions[bot] almost 2 years ago
https://www.npmjs.com/package/markdownlint-cli
Note: 0.32 introduces new failures in some repos that would need to be
addressed before moving to 0.32.x. 0.32.2 was specifically tested.
Signed-off-by: Michael Kubacki [email protected]
General release info:
https://github.com/microsoft/mu_devops/releases
Signed-off-by: Michael Kubacki [email protected]
These were previously reversed.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.1.1...v1.1.2
Published by github-actions[bot] almost 2 years ago
The checkbox exposed to contributors in a PR to determine whether
the PR has a functional impact states:
"Impacts functionality?"
This uses positive logic to simplify understanding by the user.
Currently the impact:non-functional
label is applied if the
checkbox is checked.
This change inverts the logic to apply the label as expected.
Signed-off-by: Michael Kubacki [email protected]
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.1.0...v1.1.1
Published by github-actions[bot] almost 2 years ago
Adds a new workflow and accompanying configuration files that allow
releases to automatically be drafted in repos as pull requests are
completed.
Semantic versioning is automatically determined based on the standard
set of Project Mu labels associated with the pull request.
The types of changes (e.g. bug fix, new feature, etc.) are
automatically categorized in the pull request based on the labels as
well.
This makes tracking the new Semantic Version based on the type of
changes automatic and a release is always ready. In between releases,
the draft is a nice way to see a high-level delta since the last
release.
.github/ReleaseDrafter.yml
- Single reusable workflow to maintain.github/ReleaseDraft.yml
- Configuration file for the.sync/workflows/leaf/release-draft.yml
- A leaf workflow that canProject Mu repos can easily opt into consistent release drafting by
including this leaf workflow via file sync.
I decided to allow dependabot changes into release and just not include
file sync changes since those are dev ops related and already tracked in
the mu_devops releases where they're more relevant.
Full Changelog: https://github.com/microsoft/mu_devops/compare/v1.0.0...v1.1.0
Published by makubacki almost 2 years ago
This release is incrementing the major version to baseline the version before moving to a model that will update releases as pull requests are submitted.
The main functional change since v0.1.0 in this release was setting the dependencies in Project Mu repos to a fixed version of this repo.
Full Changelog: https://github.com/microsoft/mu_devops/compare/v0.1.0...v1.0.0
Published by makubacki almost 2 years ago
This is the first Mu DevOps release 🎉
Currently, Mu DevOps serves common build content across Project Mu repos. The goal is to centralize most of the CI and build related files needed to manage the repos.
One of these components are Azure Pipelines files (see Jobs and Steps). The actual Project Mu repos have very minimal wrappers around these templates and they access the templates via a repository resource.
This is done as follows:
resources:
repositories:
- repository: mu_devops
type: github
endpoint: microsoft
name: microsoft/mu_devops
ref: main
A key reason to label this repo is to control fixed updates by setting ref
to the release tag (v0.1.0
for this release) instead of main
. Because main
is a "floating" dependency, it provides rapid adoption of changes, but we'd prefer to update in fixed increments after the repo absorbing the new mu_devops update can test the change in a pull request (that updates the ref
value).
Releases can be useful for other purposes as well. The version follows Semantic Versioning and the plan is to increment the major version on any backward incompatible change to:
Jobs
or Steps
directory of this repo.github/workflows
directory of this repoThese are the two main sources of dependencies on the content of this repo from external files at this time. The cause of major version changes in the future may change as new files and features are introduced to the repo.
Full Changelog: https://github.com/microsoft/mu_devops/commits/v0.1.0