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

230 check perforce environment #257

Merged
merged 7 commits into from
Feb 15, 2023
Merged

230 check perforce environment #257

merged 7 commits into from
Feb 15, 2023

Conversation

philou
Copy link
Contributor

@philou philou commented Feb 15, 2023

Description:

Environment check for Perforce

Fixes #230

Type of change

Please tick the appropriate option using [x]

  • Bug fix
  • New feature

Checklist:

Please tick the appropriate options using [x]

  • My PR includes tests that cover my code changes.
  • Lint and formatter run with no errors
  • All new and old tests are passing

Ahmad ATWI and others added 7 commits February 15, 2023 15:14
To be able to diagnose P4 setup issues
To be able to diagnose P4 setup issues
- Split windows specific tests for IsSubPath in own file
- handle the case where refPath is blank
To be able to diagnose P4 setup issues
….Prefix

To be able to diagnose P4 setup issues
- pass a new test case
To be able to diagnose P4 setup issues
- extract windows specific P4 tests to their own file
@philou philou linked an issue Feb 15, 2023 that may be closed by this pull request
27 tasks
@sonarcloud
Copy link

sonarcloud bot commented Feb 15, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

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

26.8% 26.8% Coverage
0.0% 0.0% Duplication

@philou philou merged commit 3e7057f into main Feb 15, 2023
@philou philou deleted the 230-check-perforce-environment branch February 15, 2023 16:49
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.

[Feature]: Have tcr check subcommand verify perforce environment
2 participants