* doc: add rules documentation
* version: add accessor for capa major version and git checkout command
* doc: rules: document version output
* doc: rules: show example error due to mismatched rule version
* doc: rules: update links
* ci: tag major rule version test
* ci: tag major rule version
* doc: update changelog
* ci: force to replace tag if exists
* ci: simplify tagging step
* Update doc/rules.md
* feat: disable tag, show error branch cmd
* doc: update major version rules branch
* Apply suggestions from code review
Co-authored-by: Willi Ballenthin <willi.ballenthin@gmail.com>
* Update capa/main.py
* black
Co-authored-by: Moritz Raabe <moritz.raabe@mandiant.com>
Co-authored-by: Moritz <mr-tz@users.noreply.github.com>
* ci: fix build
* fix: newest PyInstaller version
* fix: logo path
* fix: logo path 2
* fix: logo path 3
* fix: icon another way
* fix: remove icon for now
* ci: only build after tests succeed
* ci: add workflow_run check
Use Ana06/get-changed-files@v1.2 which removes the _head commit is ahead
of the base commit_ check. This made the action failed in not up-to-date
branches (in which rebasing is needed).
It supersedes https://github.com/fireeye/capa/pull/599
The sync GH action in capa-rules relies on a single '- *$' in the
CHANGELOG file. Check in the tests that this is the case to avoid that
it is removed.
This happened in the following PR:
https://github.com/fireeye/capa/pull/591
This caused that the new rules in the following PR were not added to the
CHANGELOG:
https://github.com/fireeye/capa-rules/pull/400
Ana06/get-changed-files@v1.1 is a fork of
https://github.com/jitterbit/get-changed-files, which supports
`pull_request_target` and allow to filter files using regular
expressions.
As we need to use `pull_request_target`, Ana06/get-changed-files@v1.1
works, but jitterbit/get-changed-files@v1 doesn't.
After using the PR template for a while, I think simplifying it will be
helpful:
- GitHub includes the commit message description automatically with the
aim of saving you time as it is sometimes also a good PR description.
With the current template, I need to cut this test and paste it into the
description section (which is really annoying!).
- Make a single simpler checklist. Add information as comment and have a
straightforward list which helps us remembering the changelog, tests and
documentation without needing to invest much time. The changelog
bulletpoint will also be used in GitHub Actions.
GitHub displays the commit's message of the tag if no description is
given, which is ugly. Use annotated tags which include a message. Use
the release link as message, as this is useful information.
