Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Experimental Pipeline Changs: Remove PR deploy, replace with npm build. #206

Closed
wants to merge 1 commit into from

Conversation

NickPhura
Copy link
Collaborator

Overview

Links to Jira tickets

n/a

Description of relevant changes

  • Add new action that just runs a local build of the app and api.

PR Checklist

A list of items that are good to consider when making any changes.

Note: this list is not exhaustive, and not all items are always applicable.

Code

  • New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
  • I have avoided duplicating code when possible, moving re-usable pieces into functions
  • I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
  • My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
  • My code changes account for null/undefined values and handle errors appropriately
  • My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

Style

  • My code follows the established style conventions
  • My code uses native material-ui components/icons/conventions when possible

Documentation

  • I have commented my code sufficiently, such that an unfamiliar developer could understand my code
  • I have added/updated README's and related documentation, as needed

Tests

  • I have added/updated unit tests for any code I've added/updated
  • I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

Linting/Formatting

  • I have run the linter and fixed any issues, as needed
    See the lint commands in package.json
  • I have run the formatter and fixed any issues, as needed
    See the format commands in package.json

SonarCloud

  • I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

@NickPhura NickPhura added the Not Ready For Review Addressing feedback and/or refactoring label Jun 28, 2023
@NickPhura NickPhura force-pushed the exp-pipeline-update branch from 340c448 to 18458a3 Compare June 28, 2023 17:25
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@codecov
Copy link

codecov bot commented Jun 28, 2023

Codecov Report

Merging #206 (18458a3) into dev (80ff67d) will increase coverage by 69.14%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           dev     #206       +/-   ##
========================================
+ Coverage     0   69.14%   +69.14%     
========================================
  Files        0      211      +211     
  Lines        0     5969     +5969     
  Branches     0      934      +934     
========================================
+ Hits         0     4127     +4127     
- Misses       0     1619     +1619     
- Partials     0      223      +223     

see 211 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@NickPhura NickPhura closed this Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Not Ready For Review Addressing feedback and/or refactoring
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant