Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Use badge in gist for rules number in README #882

Merged
merged 1 commit into from
Feb 23, 2024

Conversation

Ana06
Copy link
Member

@Ana06 Ana06 commented Feb 23, 2024

This does not rely on img.shields.io, simplifies the workflow code, and remove the need for the noisy commits in capa-rules. We still need the commits in capa to sync the submodule. I'll send a PR in capa to use the new badge in a moment.

This requires giving the token gist persmissions, which I have already done. So it should work when we merge it.

We are using gist badges in VM-Packages since a few days, in case you want to see it working. We update the number of packages when adding a new package and the the daily package failures once a day.

@Ana06 Ana06 added enhancement New feature or request CI Continous integration labels Feb 23, 2024
@Ana06 Ana06 requested a review from mr-tz February 23, 2024 07:26
@Ana06 Ana06 self-assigned this Feb 23, 2024
Ana06 added a commit to Ana06/capa that referenced this pull request Feb 23, 2024
Since the following PR, the README badge in capa is not updated anymore
via commits anymore, but in a gist:
mandiant/capa-rules#882
Ana06 added a commit to Ana06/capa that referenced this pull request Feb 23, 2024
Since mandiant/capa-rules#882, the README badge in capa is not updated
anymore via commits anymore, but in a gist.
Ana06 added a commit to Ana06/capa that referenced this pull request Feb 23, 2024
Since mandiant/capa-rules#882, the README badge in capa is not updated
anymore via commits anymore, but in a gist.
Copy link
Collaborator

@williballenthin williballenthin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice simplification!

uses: ad-m/github-push-action@master
echo "num_rules=$num_rules" >> $GITHUB_ENV
- name: Update dynamic badge gist
uses: schneegans/dynamic-badges-action@v1.7.0
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider using the release's commit hash, as described here: mandiant/capa#2000 (comment)

Copy link
Collaborator

@mr-tz mr-tz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM besides the commit hash pinning

This simplifies the workflow code and remove the need for the noisy
commits in capa-rules. We still need the commits in capa to sync the
submodule.
@Ana06 Ana06 merged commit 9c6281e into mandiant:master Feb 23, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continous integration enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants