Skip to content

Commit b7cd623

Browse files
authored
scancode-action docs #599 (#1065)
* Add documentation about the scancode-action GitHub action #599 Signed-off-by: tdruez <tdruez@nexb.com>
1 parent bb98875 commit b7cd623

File tree

4 files changed

+21
-9
lines changed

4 files changed

+21
-9
lines changed

README.rst

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,12 @@ please ask them in `Discussions <https://github.com/nexB/scancode.io/discussions
1919
If you want to contribute to ScanCode.io, start with our
2020
`Contributing <https://scancodeio.readthedocs.io/en/latest/contributing.html>`_ page.
2121

22+
A new GitHub action is now available at
23+
`scancode-action <https://github.com/nexB/scancode-action>`_
24+
to run ScanCode.io pipelines from your GitHub Workflows.
25+
Visit https://scancodeio.readthedocs.io/en/latest/automation.html to learn more
26+
about automation.
27+
2228
Build and tests status
2329
----------------------
2430

docs/automation.rst

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -73,15 +73,17 @@ automation methods such as a cron job or a git hook::
7373
By providing the required environment variables in this manner, you can execute the
7474
script with the appropriate configurations and credentials.
7575

76-
2. Integrate ScanCode.io with your CI/CD workflow
77-
-------------------------------------------------
76+
2. Integrating ScanCode.io with GitHub Workflows
77+
------------------------------------------------
7878

79-
Integrate ScanCode.io seamlessly into your CI/CD workflow by using a GitHub Action,
80-
enabling automated scans as part of your development process.
79+
Seamlessly integrate ScanCode.io into your GitHub Workflows to enable automated scans
80+
as an integral part of your development process.
8181

82-
A GitHub Action for ScanCode.io is currently under development. You can track the
83-
progress and updates on the development process by visiting the following link:
84-
https://github.com/nexB/scancode.io/issues/599
82+
Visit the `scancode-action repository <https://github.com/nexB/scancode-action>`_ to
83+
explore and learn more about the GitHub Action for ScanCode.io.
84+
The repository provides detailed information, usage instructions,
85+
and configuration options to help you incorporate code scanning effortlessly into your
86+
workflows.
8587

8688
3. Run a Local ScanCode.io app on your machine (management commands)
8789
--------------------------------------------------------------------

docs/faq.rst

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -138,4 +138,8 @@ Please refer to our :ref:`output_files` section for more details on the output f
138138
How can I trigger a pipeline scan from a CI/CD, such as Jenkins, TeamCity or Azure Devops?
139139
------------------------------------------------------------------------------------------
140140

141-
You can use the :ref:`rest_api` to automate your project or pipeline management.
141+
You can refer to the :ref:`automation` to automate your projects management.
142+
143+
Also, A new GitHub action is available at
144+
`scancode-action repository <https://github.com/nexB/scancode-action>`_
145+
to run ScanCode.io pipelines from your GitHub Workflows.

scanpipe/pipelines/inspect_packages.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ class InspectPackages(ScanCodebase):
3131
3232
Supports resolved packages for:
3333
- Python: using nexB/python-inspector, supports requirements.txt and
34-
setup.py manifests as input
34+
setup.py manifests as input
3535
3636
Supports:
3737
- BOM: SPDX document, CycloneDX BOM, AboutCode ABOUT file

0 commit comments

Comments
 (0)