|kolaente 42bd69321a||1 year ago|
|REST-Tests||1 year ago|
|docker/etc/services.d||1 year ago|
|docs||1 year ago|
|models||1 year ago|
|public/swagger||1 year ago|
|routes||1 year ago|
|vendor||1 year ago|
|.drone.yml||1 year ago|
|.gitignore||1 year ago|
|Dockerfile||1 year ago|
|Featurecreep.md||1 year ago|
|Gopkg.lock||1 year ago|
|Gopkg.toml||1 year ago|
|LICENSE||2 years ago|
|Makefile||1 year ago|
|README.md||2 years ago|
|config.yml.sample||1 year ago|
|main.go||1 year ago|
The Todo-app to organize your life.
To contribute to Vikunja, fork the project and work on the master branch.
Some internal packages are referenced using their respective package URL. This can become problematic. To “trick” the Go tool into thinking this is a clone from the official repository, download the source code into
$GOPATH/code.vikunja.io/api. Fork the Vikunja repository, it should then be possible to switch the source directory on the command line.
To be able to create pull requests, the forked repository should be added as a remote to the Vikunja sources, otherwise changes can’t be pushed.
git remote rename origin upstream git remote add origin email@example.com:<USERNAME>/vikunja.git git fetch --all --prune
This should provide a working development environment for Vikunja. Take a look at the Makefile to get an overview about the available tasks. The most common tasks should be
make test which will start our test environment and
make build which will build a vikunja binary into the working directory. Writing test cases is not mandatory to contribute, but it is highly encouraged and helps developers sleep at night.
That’s it! You are ready to hack on Vikunja. Test changes, push them to the repository, and open a pull request.