-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
0dc8176
to
3b9a355
Compare
c69785c
to
d1e284b
Compare
3603da3
to
6ba8f86
Compare
6ba8f86
to
ce4386f
Compare
ce4386f
to
1a1b5f4
Compare
acf5a9d
to
acfccc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this set of suggestions will work to streamline this part of the process.
bbd95f5
to
a2c52b9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You disabled CGo in the build
workflow but have not made a corresponding change in the release
workflow. Was this intentional? You should also update the pull request description to mention CGo being disabled (either in the build
workflow or in general) as part of the work.
@mcdonnnj good catch. I forgot to disable it in the release. I also updated the PR description. Resolved with 29eb4a6 |
29eb4a6
to
7c4c53c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ✔
Add a dispatch step to trigger a build at
cisagov/con-pca-tasks-docker
repo🗣 Description
Dispatch step depends on a release being completed.
Disabled CGO as it's not needed to run C libraries and allows for a performance boost.
💭 Motivation and context
Part of the effort to automate deployments
🧪 Testing
will be testing within this PR's gha checks
✅ Pre-approval checklist
to reflect the changes in this PR.