Automation analysis
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 15/100
Direzione di ricerca
Start with the repository's GitHub workflows and the linked Automation Thesis Wiki sections for Generate test reports and Automatic code formatting. Review the analysis and recommendations, then determine a concrete automation scope and acceptance criteria with maintainers; the issue currently asks only for feedback.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
I'm with the Software Engineering Research Group at the TU Delft, and I am investigating automations. I have looked at your repository and which GitHub workflows and Maven plugins you are using. I hope to provide you with some interesting insights about your repository! I'll give you a quick summary of what I found, and the automation tasks I recommend you to focus on next (:

| Level of maturity | Basic | Intermediate | Advanced |
|---|---|---|---|
| Collaboration | ✅ Completed this level! |
||
| ✔️ Prepare or create documentation artifacts |
✔️ Bot commits ❌ Generate documentation from source code |
❌ Publish documentation ❌ Commit validation ❌ Issues or PRs management |
|
| Code quality | ✅ Completed this level! |
||
| ✔️ Run tests ✔️ Static code style analysis |
❌ Test coverage and validity ❌ Generate test reports ❌ Automatic code formatting ❌ Static code quality analysis |
✔️ Verify packaging correctness ❌ Vulnerability scans ❌ Sign artifacts ❌ License checks |
|
| Development | ✅ Completed this level! |
||
| ✔️ Build files configuration |
✔️ Build environment configuration |
✔️ Optimization |
|
| Artifacts | ✅ Completed this level! |
||
| ✔️ Code compilation ✔️ Dependency management of artifact |
✔️ Build tasks, resources and configuration ✔️ Packaging ✔️ Release tagging ✔️ Publish artifacts to a registry |
✔️ Containerization ❌ Generate source and metadata artifacts ❌ Generate release notes ❌ Source control management |
And now? Next steps!
It is not always clear which automation tasks should be prioritized. It is however important to balance your automation efforts, as a uniform level of maturity is most productive. I'm here to help! Below is a list of tasks that you can work on to help level up your maturity across the automation domains:
- Implement Generate test reports; implemented by 10% of GitHub repositories
- Implement Automatic code formatting; implemented by 10% of GitHub repositories
What do you think?
Do you think my analysis is correct, do these recommendations help you? Or have I missed something?
For my master's thesis I'm doing research into the use of automations in GitHub repositories. With my findings, I want to see if I can help out developers with what automations they could focus on. Do you want to help me out? Leaving a response is much appreciated!
If you have any other Java/Maven projects you'd like analyzed, you can send me the repositories and I can analyze them for you!
- Lingua principale
- Python
- Stelle
- 596
- Fork
- 164
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di runtimeverification/k
-
bug
Difficoltà 3/5 Mezza giornata Idoneità per principianti 75/100
runtimeverification/k#4941 ·
-
Introduce composable symbolic execution interface in pyxForse di nuovo libera @Stevengre l’ha presa 118 giorni fa e non c’è nessuna pull request aperta. Aperta
runtimeverification/k#4939 · 1 assegnatario ·
-
Concolic ExplorerAperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 32/100
runtimeverification/k#4937 ·
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
runtimeverification/k#4936 ·
-
Accelerating all-path reachability proofs with one-path reachability proofsForse di nuovo libera @Stevengre l’ha presa 124 giorni fa e non c’è nessuna pull request aperta. Apertatype:epic
runtimeverification/k#4934 · 4 commenti · 1 assegnatario ·
Tutte le issue di runtimeverification/k
Issue simili
-
bug documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
awslabs/visual-asset-management-system#514 ·
I maintainer di solito rispondono entro 1 giorno
-
backend bug spec:REQ-053
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
nolte/kamerplanter#2547 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
EleutherAI/lm-evaluation-harness#4425 ·
I maintainer di solito rispondono entro 1 giorno
-
Gemini: respect PLANNING_DISABLED=1 in lifecycle context hooksForse già presa @AmariAugustin l’ha presa oggi. Apertabug good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
OthmanAdi/planning-with-files#329 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
wr.dynamodb.read_items returns [{}] for a single partition value that does not existForse già presa @auraseb l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
aws/aws-sdk-pandas#3520 ·
I maintainer di solito rispondono entro 2 giorni