Automation analysis #865
simcha-vos-from-tu-delft
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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 (:
✅ Completed this level!
✔️ Bot commits
❌ Commit validation
❌ Issues or PRs management
❌ Static code style analysis
❌ Generate test reports
❌ Automatic code formatting
❌ Static code quality analysis
❌ Vulnerability scans
❌ Sign artifacts
❌ License checks
✅ Completed this level!
✅ Completed this level!
✔️ Dependency management of artifact
✔️ Packaging
✔️ Release tagging
✔️ Publish artifacts to a registry
✔️ Containerization
❌ 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:
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!
Beta Was this translation helpful? Give feedback.
All reactions