-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create tech stack docs (techstack.yml and techstack.md) #22
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 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
pgwilliams
force-pushed
the
develop
branch
2 times, most recently
from
March 21, 2024 15:04
16c0bf4
to
fef5b58
Compare
dmcgihtsdo
force-pushed
the
develop
branch
2 times, most recently
from
July 31, 2024 12:00
08e9af2
to
de3944a
Compare
pgwilliams
force-pushed
the
develop
branch
2 times, most recently
from
August 5, 2024 06:39
2b116f5
to
4c0c6fd
Compare
astro-snail
force-pushed
the
develop
branch
2 times, most recently
from
August 21, 2024 13:55
184074f
to
094f4b7
Compare
pgwilliams
force-pushed
the
develop
branch
12 times, most recently
from
September 6, 2024 10:04
51599fb
to
f180288
Compare
pgwilliams
force-pushed
the
develop
branch
5 times, most recently
from
October 2, 2024 14:36
0d062a3
to
13d4f29
Compare
pgwilliams
force-pushed
the
develop
branch
3 times, most recently
from
October 9, 2024 12:12
6d493af
to
445eb42
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.yml
andtechstack.md
.techstack.yml
contains data on all the technologies being used in this repo.techstack.md
is a visualization of the YML file and displays the tech stack data in a pretty Markdown file.💡 Protip:
techstack.md
contains 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: