Skip to content

ProjectDiscovery's Composite Actions

License

Notifications You must be signed in to change notification settings

projectdiscovery/actions

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Actions

ProjectDiscovery's composite actions.

Releases

  • default HEAD branch (master) - latest code changes and updates, which might not have undergone thorough testing and quality assurance; use at your own risk.
  • Major version branch (e.g. vN) - contains stable releases; considered production-ready.
  • dotfiles branch - contains configuration files for setting up development environments used across actions. This branch is NOT subject to frequent changes; modify with caution.

Development

Add a workflow test for each new action to ensure quality and reliability and make sure new changes DO NOT break existing functionality so that it can be promoted to the major version branch.

For maintainers:

When creating release tags, follow the SemVer format (vX.Y.Z).

flowchart TB
    feat["Feature/patch branch"]
    master
    major["Major version branch"]
    incremented@{label: "Incremented branch\n(e.g. vX.Y.1, vX.1.Z)"}
    tag@{ shape: tag-rect, label: "Release tag\n(e.g. vX.Y.1, vX.1.Z)" }

    feat -->|merge| incremented
    incremented -->|tested & stable| major
    major <--o|rebase| master
    master --> tag
Loading

Note

All changes must be applied to the default HEAD branch as well as the respective major version branch.

License

MIT.

About

ProjectDiscovery's Composite Actions

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks