Automation analysis

[simchavos]

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	‎ ⚠️ Still working on this level!
	❌ Prepare or create documentation artifacts	❌ Generate documentation from source code ❌ Commit validation ❌ Bot commits	✔️ Issues or PRs management ❌ Publish documentation
Code quality	‎ ⚠️ Still working on 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	‎ ⚠️ Still working on this level!
	✔️ Code compilation ❌ Dependency management of artifact	✔️ Packaging ❌ Build tasks, resources and configuration ❌ Release tagging ❌ Publish artifacts to a registry	✔️ Generate release notes ✔️ Source control management ✔️ Containerization ❌ Generate source and metadata artifacts

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 Run tests; implemented by 23% of GitHub repositories
• Implement Prepare or create documentation artifacts; implemented by 18% 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!

[eddumelendez]

Hi, we use maven as a dependency management and have lot of tests.

We use spotless for code formatting and checkstyle for static code analysis.

[simchavos]

Hi, we use maven as a dependency management and have lot of tests.

We use spotless for code formatting and checkstyle for static code analysis.

Appreciate your feedback! I'll look into what went wrong there.. You're right; your codebase seems to cover a ton of automations!

[simchavos]

Hi, we use maven as a dependency management and have lot of tests.

We use spotless for code formatting and checkstyle for static code analysis.

Hello,
I have one final question to help me better understand your interest in tools like this, because you seem to have a lot of automations present. Given that this tool would be detecting all your automations well, would you be interested in using it, as a way to easily report on your current state of automations and gain recommendations for future automation steps? For example, if its available as a badge in your readme?
Thank you!