-
Notifications
You must be signed in to change notification settings - Fork 1
Create tech stack docs (techstack.yml and techstack.md) #22
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
Open
stack-file
wants to merge
28
commits into
develop
Choose a base branch
from
tech-stack-file
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ecret not private.
…so to the point where it shows as being Up-to-date or Behind the parent branch
…oc and override file
…odifying Historical Associations. Also improve file parsing issue reporting
… spreadsheet, and report lexical matches wihtout 'O/E'
…x) and cousin concepts (no prefix) for OE/CO work
…RF2. Optionally include Inactivation Indicator in prettyPrint
… based on 'NOS' and '[' in FSN
…e next. Also don't report a concept if already reported as sibling Also flag when siblings differ in their historical association targets
…ndicator is included in output
…onents.java file has been modified to set acceptability for both US and GB cloning.
…bility map is also updated, such that check for US + GB preferred terms will pass
16c0bf4 to
fef5b58
Compare
fd86819 to
390523a
Compare
4cc0387 to
924a84a
Compare
e7c2078 to
832d2eb
Compare
e3382dd to
d019e3c
Compare
9fe62e3 to
0a7bf31
Compare
6f08723 to
2c0a2f2
Compare
3445e40 to
b1d5d37
Compare
62fa775 to
cff2748
Compare
516105d to
bb3f634
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding tech stack documentation to allow anyone to easily see what is being used in this repo without digging through config files. Two files are being added:
techstack.ymlandtechstack.md.techstack.ymlcontains data on all the technologies being used in this repo.techstack.mdis a visualization of the YML file and displays the tech stack data in a pretty Markdown file.💡 Protip:
techstack.mdcontains a comment at the top of the file that the following README snippet (with and without the logos) at the top of the file as a comment:<--- Readme.md Snippet without images Start --->
Tech Stack
IHTSDO/reporting-engine is built on the following main stack:
Full tech stack here
<--- Readme.md Snippet without images End --->
Get the code:
<--- Readme.md Snippet with images Start --->
Tech Stack
IHTSDO/reporting-engine is built on the following main stack:
Full tech stack here
<--- Readme.md Snippet with images End --->
Get the code: