Skip to content

Conversation

@eyitemi-paystack
Copy link

@eyitemi-paystack eyitemi-paystack commented Aug 5, 2021

Commit to add CodeQL workflow for Static App Security Testing.

Description

Commit to add CodeQL workflow for Static App Security Scanning.

Motivation and Context

This commit allows us to run Github CodeQl as Github Actions and use CodeQL as a Static Application Security Testing tool to identify security vulnerabilities in code before it gets merged to master and deployments made.

Acceptance Criteria

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful. (Please rebase, removing useless commits if not)
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My code follows the code style of this project.
  • My change requires change(s) to the environment.
  • My change requires change(s) to the database.
  • Other information.

Commit to add CodeQL workflow for Static App Security Testing.

Description
-----------
Commit to add CodeQL workflow for Static App Security Scanning.


Motivation and Context
----------------------
This commit allows us to run Github CodeQl as Github Actions and use CodeQL as a Static Application Security Testing tool to identify security vulnerabilities in code before it gets merged to `master` and deployments made.


Acceptance Criteria
-------------------
Ability to restart instances without tsagent throwing an error

Screenshots (if appropriate)
----------------------------

Types of changes
----------------
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist
---------
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->

- [x] My pull request addresses exactly one patch/feature.
- [x] I have created a branch for this patch/feature.
- [x] Each individual commit in the pull request is meaningful. (Please rebase, removing useless commits if not)
- [ ] I have added tests to cover my changes.
- [ ] All new and existing tests passed.
- [x] My code follows the code style of this project.
- [ ] My change requires change(s) to the environment.
      <!--- Describe the environment changes if any-->
- [ ] My change requires change(s) to the database.
      <!--- Describe the database changes if any-->
- [ ] Other information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants