Skip to content

Differentiate CompositeAction nodes by version  #97

Open
Open
Differentiate CompositeAction nodes by version #97
Assignees
oreenlivnicode
Labels
featuregood first issueGood for newcomers

Description

@oreenlivnicode
oreenlivnicode
opened on Oct 25, 2023

Currently, Composite Action nodes lack attached version information, which prevents us from querying for vulnerabilities that exist in specific versions.
To address this, we should represent each version of a Composite Action as a separate node.

Activity

  1. oreenlivnicode
    added
    good first issueGood for newcomers
    feature
    on Oct 25, 2023
  2. oreenlivnicode
    changed the title [-]Differentiate CompositeAction nodes by version or hash[/-] [+]Differentiate CompositeAction nodes by version [/+] on Oct 25, 2023
  3. oreenlivnicode
    self-assigned this
    on Oct 25, 2023

  4. oreenlivnicode commented on Oct 31, 2023

    @oreenlivnicode
    oreenlivnicode
    on Oct 31, 2023
    ContributorAuthor

    #110

  5. oreenlivnicode
    linked a pull request that will close this issueFeature - Add Version To Composite Action and Reusable Workflow #110on Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featuregood first issueGood for newcomers

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions