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

Create tech stack docs (techstack.yml and techstack.md) #22

Open
wants to merge 28 commits into
base: develop
Choose a base branch
from

Conversation

stack-file[bot]
Copy link

@stack-file stack-file bot commented Mar 21, 2024

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 and techstack.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:

## Tech Stack
IHTSDO/reporting-engine is built on the following main stack:

- [Groovy](https://groovy-lang.org/) – Languages
- [Java](https://www.java.com) – Languages
- [Spring Framework](https://spring.io/projects/spring-framework) – Frameworks (Full Stack)
- [ActiveMQ](http://activemq.apache.org/) – Message Queue
- [JUnit](http://junit.org/) – Testing Frameworks
- [Logback](https://logback.qos.ch/) – Log Management
- [SLF4J](http://slf4j.org/) – Log Management
- [Spock Framework](http://spockframework.org/) – Testing Frameworks
- [Apache Camel](https://camel.apache.org/) – Platform as a Service
- [Shell](https://en.wikipedia.org/wiki/Shell_script) – Shells

Full tech stack [here](/techstack.md)

<--- 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:

## Tech Stack
IHTSDO/reporting-engine is built on the following main stack:

- <img width='25' height='25' src='https://img.stackshare.io/service/997/default_7ff5fcd857f42ad25149f659693d8930bffddf14.png' alt='Groovy'/> [Groovy](https://groovy-lang.org/) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/995/K85ZWV2F.png' alt='Java'/> [Java](https://www.java.com) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/2006/spring-framework-project-logo.png' alt='Spring Framework'/> [Spring Framework](https://spring.io/projects/spring-framework) – Frameworks (Full Stack)
- <img width='25' height='25' src='https://img.stackshare.io/service/1062/default_08edb6f82e2c79424efc1e297ab096e50acd8e0b.jpg' alt='ActiveMQ'/> [ActiveMQ](http://activemq.apache.org/) – Message Queue
- <img width='25' height='25' src='https://img.stackshare.io/service/2020/874086.png' alt='JUnit'/> [JUnit](http://junit.org/) – Testing Frameworks
- <img width='25' height='25' src='https://img.stackshare.io/service/2923/05518ecaa42841e834421e9d6987b04f_400x400.png' alt='Logback'/> [Logback](https://logback.qos.ch/) – Log Management
- <img width='25' height='25' src='https://img.stackshare.io/service/2805/05518ecaa42841e834421e9d6987b04f_400x400.png' alt='SLF4J'/> [SLF4J](http://slf4j.org/) – Log Management
- <img width='25' height='25' src='https://img.stackshare.io/service/5548/UB74SoK2_400x400.png' alt='Spock Framework'/> [Spock Framework](http://spockframework.org/) – Testing Frameworks
- <img width='25' height='25' src='https://img.stackshare.io/service/3276/xWt1RFo6_400x400.jpg' alt='Apache Camel'/> [Apache Camel](https://camel.apache.org/) – Platform as a Service
- <img width='25' height='25' src='https://img.stackshare.io/service/4631/default_c2062d40130562bdc836c13dbca02d318205a962.png' alt='Shell'/> [Shell](https://en.wikipedia.org/wiki/Shell_script) – Shells

Full tech stack [here](/techstack.md)

astro-snail and others added 28 commits March 13, 2024 19:39
…so to the point where it shows as being Up-to-date or Behind the parent branch
…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
…e next.

Also don't report a concept if already reported as sibling

Also flag when siblings differ in their historical association targets
…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 pgwilliams force-pushed the develop branch 2 times, most recently from 16c0bf4 to fef5b58 Compare March 21, 2024 15:04
@pgwilliams pgwilliams force-pushed the develop branch 6 times, most recently from 6d493af to 445eb42 Compare October 9, 2024 12:12
@astro-snail astro-snail force-pushed the develop branch 2 times, most recently from 2f57ef5 to f59735e Compare October 15, 2024 13:59
@pgwilliams pgwilliams force-pushed the develop branch 4 times, most recently from d0a76dd to 7582748 Compare October 17, 2024 00:36
@pgwilliams pgwilliams force-pushed the develop branch 2 times, most recently from d93393f to ac9aad3 Compare October 29, 2024 19:52
@pgwilliams pgwilliams force-pushed the develop branch 9 times, most recently from 24f4e52 to 04be77b Compare November 18, 2024 11:45
@pgwilliams pgwilliams force-pushed the develop branch 2 times, most recently from 593c77a to 043989f Compare November 20, 2024 19:28
@pgwilliams pgwilliams force-pushed the develop branch 3 times, most recently from f7cb045 to b3b4cad Compare December 10, 2024 11:43
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.

4 participants