Our great sponsors
-
-
I want the opposite - tickets-as-code part of the git repo. Something like SIT[1]. Fossil has it, but today's standard DVCS is git.
There are 2 trends here:
1. Everything-as-a-code stored in the git repo in a text format, close to the actual source code. If you store documention-as-a-code, diagrams-as-a-code, IaaC, tests-as-a-code, loadtesting-as-a-code, etc. - then why not issues/tickets as code also?
2. Reduce number of tools/service you use in order to eliminate impedance mismatch and simplify workflows, and remove barriers to collaboration. For example if you standardize on Github, then you can use Guthub Issues, Projects, Packages, Actions, Codespaces, etc. And most developers are already having Github a/c.
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
This reminded me of toodles[0], a nice project you can use to visualize TODO comments as issues. I didn't have the chance to try it, but I'm looking forward it for my next project
-
-
I made a prompt todo reminder that could be nicely completed by your project! https://github.com/netgusto/tax
Also, reminds me of the blockchain oracle systems and smart contracts.
Cool idea, neat project!
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.