Prepare for GitHub Action v3.0.0 release

CHANGELOG.md

@@ -1,22 +1,3 @@
-## [1.5.1](https://github.com/fortify/github-action/compare/v1.4.0...v1.5.1) (2024-11-01)
-
-
-### Features
-
-* FoD: Add support for creating application through `DO_SETUP` ([2d91e3c](https://github.com/fortify/github-action/commit/2d91e3c5c405391e5ee2cfe725a77b0ded38dcd0))
-* FoD: Automatically set `--app-owner` if `FOD_USER` is configured ([345ddda](https://github.com/fortify/github-action/commit/345ddda04de863b34e9566df5ea088f5872eeef4))
-* FoD: Improve handling of `--copy-from` option in `SETUP_EXTRA_OPTS` ([2d91e3c](https://github.com/fortify/github-action/commit/2d91e3c5c405391e5ee2cfe725a77b0ded38dcd0))
-* Major documentation usability improvements ([22ea8e9](https://github.com/fortify/github-action/commit/22ea8e9ef9edb24e364d1dc66230649726ad450c))
-* Simplify setup of Debricked scans on FoD ([7c25788](https://github.com/fortify/github-action/commit/7c25788b4c57582d2039d70a1ad9aeb228e34c6c))
-* Update fcli to 2.9.0 ([2d91e3c](https://github.com/fortify/github-action/commit/2d91e3c5c405391e5ee2cfe725a77b0ded38dcd0))
-* Update ScanCentral Client to 24.4.0 ([f3246ac](https://github.com/fortify/github-action/commit/f3246ac1d35a20a34df0a2d404479f1fabeae574))
-
-
-### Bug Fixes
-
-* Improve parsing of boolean flags in `*_EXTRA_OPTS` ([2d91e3c](https://github.com/fortify/github-action/commit/2d91e3c5c405391e5ee2cfe725a77b0ded38dcd0))
-* Update Debricked CLI to 2.1.7 ([2d91e3c](https://github.com/fortify/github-action/commit/2d91e3c5c405391e5ee2cfe725a77b0ded38dcd0))
-
 # Changelog
 
 ## [2.2.0](https://github.com/fortify/github-action/compare/v2.1.1...v2.2.0) (2025-11-19)

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to Fortify GitHub Actions
+# Contributing to Fortify GitHub Action
 
 ## Contribution Agreement
 
@@ -10,33 +10,32 @@ Contributions like bug fixes and enhancements may be submitted through Pull Requ
 ## Information for Developers
 
 ### Repository initialization
-After cloning this repository, please run ./configure.sh to install npm modules and configure git hooks. When adding a new NodeJS-based action, you'll need to update `<repo-root>/configure.sh` to add the action directory to the for-loop.
-
-### Action documentation
-Action documentation is generated from the `doc-resources` directory, using functionality provided by https://github.com/fortify/shared-doc-resources. The `doc-resources` directory contains the following:
-
-* `action/_generic/**/*`: Generic includes referenced from action documentation
-* `action/_root/readme.md`: Documentation for the top-level action
-* `action/<action-name>`: 
-    * `readme.md`: Documentation for `<action-name>` sub-action
-    * `nocomments.env-*.md`: Markdown table rows describing environment variable inputs
-    * `nocomments.snippet-*.md`: Sample YAML snippets
-* `repo-devinfo.md`: Information for developers
-* `repo-usage.md`: Used to generated top-level USAGE.md, just refers to README.md
-* `template-values.md`: Defines variables used in documentation resources
-* `templates/README.template.md`: Template for the top-level `README.md` file
-* `templates/<action-name>/README.template.md`: Template for the README.md file for each sub-action
-* `update-repo-docs.sh`: Script to generate documentation resources
-
-If you need to update the documentation for an existing action, you'll want to edit the corresponding `action/<action-name>/readme.md` file or the included files. 
-
-When adding a new action, you should:
-* Create a corresponding directory in the `doc-resources/templates` directory
-* Copy an existing `README.template.md` from one of the other action template directories
-* Change the header and include statement in the new `README.template.md` to match the new action
-* Create a new `action/<action-name>/readme.md` file in the `doc-resources` directory
-
-After any documentation updates, you may want to manually run `doc-resources/update-repo-docs.sh` to verify whether all includes can be found, and to review the generated README.md files for each action.
+After cloning this repository, please run `./configure.sh` to install npm modules and configure git hooks.
+
+### Documentation structure
+Documentation is generated from the `doc-resources` directory using functionality provided by https://github.com/fortify/shared-doc-resources. The structure is straightforward:
+
+* `repo-intro.md`: Introduction text included in README.md
+* `repo-usage.md`: Usage instructions included in USAGE.md
+* `repo-resources.md`: Links to resources (contributing, license, etc.)
+* `repo-devinfo.md`: Information for developers (this file)
+* `repo-usage-text.md`: Include file with links to detailed documentation (used in both intro and usage)
+* `template-values.md`: Variables used throughout the documentation
+* `update-repo-docs.sh`: Script to regenerate README.md, USAGE.md, and other files
+
+To update documentation, edit the appropriate `.md` files in `doc-resources/`, then run `doc-resources/update-repo-docs.sh` to regenerate the top-level documentation files.
+
+### Building the action
+
+The action uses the `@fortify/setup` NPM package published to [npmjs.org](https://www.npmjs.com/package/@fortify/setup). To build:
+
+```bash
+cd setup
+npm install
+npm run build
+```
+
+This creates a bundled `dist/index.js` file that includes all dependencies. The action is ready to use once the dist directory is committed.
 
 <!-- END-INCLUDE:repo-devinfo.md -->