find repo todos, create Jira tickets and reference todos in the tickets.
mvn package
java -jar target/jubilant-todo-tribble-1.0.0-SNAPSHOT.jar
copy templates/application-local.yaml
-> <APP_DIR>/application.yaml
and fill with your own data
find repo todos, create Jira tickets and reference todos in the tickets.
License: Apache License 2.0
find repo todos, create Jira tickets and reference todos in the tickets.
mvn package
java -jar target/jubilant-todo-tribble-1.0.0-SNAPSHOT.jar
copy templates/application-local.yaml
-> <APP_DIR>/application.yaml
and fill with your own data
Currently git does not ignore the credentials class which is pretty annoying for every commit
Let's read a Credentials file or our already exisiting application.yaml even for the tests.
Read codebase of arbitrary repo and walk path
Should have
Out of scope: easy deployment process. Building on whatever server and restarting should suffice for the start.
case 1,2 (consider context change) / 3 (word difference) should be done in another issue
We do not really want to use one standard component in all Jira issues. Thats why we want to be able to select a component that already exists or create a new component.
Java?
Kotlin?
Travis should be good for the job
https://docs.travis-ci.com/user/languages/java/#Projects-Using-Maven
build on every commit
build on develop branch
build on master branch
notify committer on error
do not forget fancy badge in README ;-)
[-] test if commit on change from failure to success works - Currently there is no mail on build change from failure to success. Because this is not that important. Thats why this ticket will be closed.
.. rather than scanning the whole file tree over and over again
patch
) https://api.github.com/repos/Husterknupp/jubilant-todo-tribble/commits/30fd93abf61d32ae9132def3f01c67aa76dc4da2mvn clean package -U
should lead to
BUILD SUCCESS
maven outputPlease provide a console output with details for a broken build.
Programmatically create an issue
read this and do it: https://docs.travis-ci.com/user/deployment
It would be nice if todos would be added to a ticket that I'm anyway working on so that I can make the progress of an issue more transparent
Either by looking in the commit message or by parsing the todo itself
format could be like
for Jira
[DEV-123] comited some code
// todo something needs to be done (DEV-123)
and this for github
#20 comited some code
// todo something needs to be done (20)
.. and not create tokens with every new request. Avoid being the session creation leader
on GET /stats
show me
Format should look like this
( ) Todo in ${repoId} (branch ${branchName}) - ${fileUrl} Line ${lineNumber}
Dunno if we need it or want it. Just in case, I found this one might be interesting to try out.
Structurizr http://flip.it/V5x8WX
Currently one can specify only one component to scan. It makes sense to enable more than one repo.
store:
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.