github-starter-workflows/repo-analysis-partner

repo-analysis-partner

Check out tech_stacks.yml for the list of tech_stacks detected by repo analysis on GitHub. To request support for detecting any new tech_stack please raise an issue on this repository.

repo-analysis-partner's Issues

Azure Data Factory support as a new `tech_stack`

Name of the tech_stack
The new tech_stack suggested is Azure Data Factory.

File extensions to look for in the repository
The repository must have a .json file.

Content/Regex to look for in the above-mentioned filename/extensions

The presence of the following JSON content:

{
    "scripts":{
        "build":"node node_modules/@microsoft/azure-data-factory-utilities/lib/index"
    },
    "dependencies":{
        "@microsoft/azure-data-factory-utilities":"^0.1.5"
    }
}

Kompose support new tech_stack

Name of the tech_stack
A distinct name for the tech_stack
Kompose

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.

Kompose has a very fluid structure -- could match the helm detection, or could just have a grouping of yaml files. Would expect to see docker-compose files, as well as files that end with yaml/yml

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

*.yaml

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

these fields, in any yaml file

apiVersion:
kind:

Additional context
Add any other context or screenshots about the feature request here.
https://github.com/kubernetes/kompose/blob/master/docs/user-guide.md

Texh stacks

Name of the tech_stack
A distinct name for the tech_stack

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

Sample public repository which we can add to our test suite
Provide a public repo which contains relevant files and is expected to have the above mentioned tech_stack. This repo will be added to our regression test suite.

**Additional context**
Add any other context or screenshots about the feature request here.

Astro support as new `tech_stack`

Name of the tech_stack
Astro

Filenames to look for in the repository
package.json
astro.config.mjs

File extensions to look for in the repository
.js
.ts
.astro

Content/Regex to look for in the above-mentioned filename/extensions
package.json file must include svelte in the dependencies list:
"dependencies": {
"astro":

Additional context
Example repo
Example repo 2

Laravel support as a new `tech_stack`

Name of the tech_stack
The new tech_stack suggested is Laravel.

Filenames to look for in the repository
The repository must have a composer.json file.

Content/Regex to look for in the above-mentioned filename/extensions

{
    "require": {
        "laravel/framework": "5.5.*",
    }
}

Technological Book

**Name of the "technological book" ** A distinct name for the tech_stack`

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

Sample public repository which we can add to our test suite
Provide a public repo which contains relevant files and is expected to have the above mentioned tech_stack. This repo will be added to our regression test suite.

Additional context
Add any other context or screenshots about the feature request here.

Jekyll support as new `tech_stack`

Name of the tech_stack
Jekyll

Filenames to look for in the repository (not all of them will be present)
_config.yml
_config.toml
Gemfile

File extensions to look for in the repository (not all of them will be present)
.html
.js
.css

Additional context
Jekyll is a framework written in Ruby and some of the Jekyll repositories will be detected as Ruby while others not

Example repo listing Ruby as one of the languages: lone-wolf-theme

Example repo not listing Ruby as one of the languages: mvm

Yo

https://github.com/github-starter-workflows/repo-analysis-partner/blame/0b80be121c78ca30896c6cbdb209b89cc5f3d0e0/tech_stacks.yml#L15C9-L15C9

Symfony support as a new `tech_stack`

Name of the tech_stack
The new tech_stack suggested is Symfony.

Filenames to look for in the repository
The repository must have a composer.json file.

Content/Regex to look for in the above-mentioned filename/extensions

{
    "require": {
        "symfony/framework-bundle": "4.4.*",
    }
}

Kustomize support new `tech_stack`

Name of the tech_stack
A distinct name for the tech_stack
Kustomize

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.
kustomization.yaml

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

.yaml

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

n/a

Additional context
Add any other context or screenshots about the feature request here.
https://github.com/kubernetes-sigs/kustomize/blob/master/examples/helloWorld/README.md

Next.js support as new `tech_stack`

Name of the tech_stack
Next

Filenames to look for in the repository
package.json
Optionally, it could also include next.config.json

File extensions to look for in the repository
.js
.ts

Content/Regex to look for in the above-mentioned filename/extensions
package.json file must include next in the dependencies list:
"dependencies": {
"next":

Additional context
Example repo

Phoenix support new tech_stack

Name of the tech_stack
A distinct name for the tech_stack
Phoenix

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.
mix.lock

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.
.ex, .exs, .heex

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore
phx
phoenix
Phoenix.Controller
Phoenix.Endpoint

Additional context
Add any other context or screenshots about the feature request here.
Sample Phoenix app
https://github.com/shundor/phoenix-hello-world

Gatsby support as new `tech_stack`

Name of the tech_stack
Gatsby

Filenames to look for in the repository (not all of them will be present)
gatsby-config.js
package.json

File extensions to look for in the repository (not all of them will be present)
.html
.js
.ts
.css

Content/Regex to look for in the above-mentioned filename/extensions
In the package.json file, search for "dependencies": { "gatsby":

Additional context
Example repo

Svelte support as new `tech_stack`

Name of the tech_stack
Svelte

Filenames to look for in the repository
package.json
svelte.config

File extensions to look for in the repository
.js
.ts
.svelte

Content/Regex to look for in the above-mentioned filename/extensions
package.json file must include svelte in the dependencies list:
"dependencies": {
"svelte":

Additional context
Example repo
Example repo 2

Improved support for `Kubernetes` tech stack

Name of the tech_stack
Kubernetes

File extensions to look for in the repository
*.yaml

Content/Regex to look for in the above-mentioned filename/extensions
Having any of the following in the YAML files

kind: Binding
kind: ComponentStatus
kind: ConfigMap
kind: Endpoints
kind: Event
kind: LimitRange
kind: Namespace
kind: Node
kind: NodeProxyOptions
kind: PersistentVolumeClaim
kind: PersistentVolume
kind: Pod
kind: PodAttachOptions
kind: Eviction
kind: PodExecOptions
kind: PodPortForwardOptions
kind: PodProxyOptions
kind: PodTemplate
kind: ReplicationController
kind: Scale
kind: ReplicationController
kind: ResourceQuota
kind: Secret
kind: ServiceAccount
kind: TokenRequest
kind: Service
kind: ServiceProxyOptions

List above is generated via this command:

for apipath in $(kubectl api-versions | sort | sed '/\//{H;1h;$!d;x}'); do
  version=${apipath#*/}
  api=${apipath%$version}
  api=${api%/}
  prefix="/api${api:+s}/"
  api=${api:-(core)}
  >&2 echo "${prefix}${apipath}: ${api}/${version}"
  kubectl get --raw "${prefix}${apipath}" | jq -r --arg api "${api}/${version}" '.resources | sort_by(.name) | .[]? | "kind: \(.kind)"'
done

Additional context
Right now, the Get started with GitHub Actions is not recommending Kubernetes actions for repositories that have Kubernetes manifests. This proposal is to improve the detection logic.

Helm Support for new `tech_stack`

Name of the tech_stack
A distinct name for the tech_stack
Helm

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.

Chart.yaml in the same directory as a directory named templates

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

yaml files in a directory named templates

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

These three fields in the file named chart.yaml
apiVersion: The chart API version (required)
name: The name of the chart (required)
version: A SemVer 2 version (required)

Additional context
Add any other context or screenshots about the feature request here.
https://helm.sh/docs/topics/charts/

Vue support as new `tech_stack`

Name of the tech_stack
Vue

Filenames to look for in the repository
This repository must include a index.html file
and/or
This repository must include a package.json file

File extensions to look for in the repository
.vue
.js
.ts
.html

Content/Regex to look for in the above-mentioned filename/extensions
In the package.json file, search for "dependencies": { "vue":
In the index.html file, search for <script src="https://cdn.jsdelivr.net/npm/vue"></script> or <script src="https://cdn.jsdelivr.net/npm/vue/dist/vue.js"></script>

Additional context
GitHub already detects Vue as a language, as it can be seen in this repo vue-admin

https://github.com/github-starter-workflows/repo-analysis-partner/actions

Name of the tech_stack
A distinct name for the tech_stack

Filenames to look for in the repository
This defines the name of the file used as the criteria of detection. For eg, the presence of yarn.lock is the detection criteria for Yarn.

File extensions to look for in the repository
This defines the extensions of files used as the criteria of detection. For eg, the presence of .csproj extension is a detection criteria for AspNetCore.

Content/Regex to look for in the above-mentioned filename/extensions
This defines the content to look for in the file with the name/extensions defined above. For eg, the presence of <Project Sdk="Microsoft.NET.Sdk.Web"> in a file with extension .csproj is the detection criteria for AspNetCore

Sample public repository which we can add to our test suite
Provide a public repo which contains relevant files and is expected to have the above mentioned tech_stack. This repo will be added to our regression test suite.

Additional context
Add any other context or screenshots about the feature request here.

Nuxt support as new `tech_stack`

Name of the tech_stack
Nuxt

Filenames to look for in the repository
package.json
Optionally, it could also include nuxt.config.json

File extensions to look for in the repository
.js
.ts
'.vue'

Content/Regex to look for in the above-mentioned filename/extensions
package.json file must include nuxt in the dependencies list:
"dependencies": {
"nuxt":

Additional context
Example repo