Giters
FirelyTeam
/
firely-terminal-pipeline
Run Firely.Terminal as GitHub Actions
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
9
Watchers:
13
Issues:
18
Forks:
5
FirelyTeam/firely-terminal-pipeline Issues
REST operations are always sent as application/fhir+xml
Closed
5 months ago
Conditional running of action steps could be made more concise using `run.steps[*].if`
Updated
a year ago
Comments count
1
`fhir check` likely won't ever fail without specifying the `--fail` flag
Updated
a year ago
Expose sushi version as parameter
Closed
2 years ago
Comments count
1
Remove one-by-one Firely Terminal validation
Closed
2 years ago
Comments count
2
Run sushi before .NET validation and QC
Closed
2 years ago
Comments count
1
Pipeline will fail if fhir restore fails even if continue on fail is enabled
Updated
2 years ago
Validation problems because of the incorrect FHIR version
Closed
2 years ago
Comments count
2
Flag to exclude file extensions
Closed
2 years ago
Comments count
2
Java validator will throw an error if JAVA_VALIDATION_OPTION is empty
Updated
2 years ago
PATH_TO_CONFORMANCE_RESOURCES cannot contain folders with spaces
Updated
2 years ago
Feature: use dependencies from sushi-config.yaml
Updated
2 years ago
Provide nice colors and statistics for output
Updated
2 years ago
Allow non-FHIR files in folders
Closed
2 years ago
Comments count
1
Create documentation that package.json is required.
Closed
2 years ago
Allow running multiple steps within one job
Closed
2 years ago
Comments count
1
Improvements to documentation
Closed
2 years ago
Comments count
2
Commit output from sushi to GitHub repository
Closed
2 years ago
Comments count
1