Giter Club home page Giter Club logo

jkl's Introduction

jkl

jkl is a library for programmatically interacting with a JIRA installation. It comes with a command line program (also called jkl) which allows you to interact with JIRA via the command line.

Installation

To use the library, simply import it into your application: import "github.com/otremblay/jkl"

To install the command line application: First, make sure you have a working go environment: https://golang.org/doc/install

Then, execute the following command from your shell:

$ go get github.com/otremblay/jkl/cmd/jkl

Usage

Make sure you create a ~/.jklrc file in your home directory, it should contain at a minimum:

JIRA_ROOT="https://jira.example.com/"
JIRA_USER="myusername"
JIRA_PASSWORD="mypassword"
JIRA_PROJECT="DPK"

Those values are for example only, your setup will be different.

TODO: Finish writing usage instructions

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

jkl's People

Contributors

avanier avatar gabeguz avatar ls-olivier-tremblay avatar otremblay avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

jkl's Issues

Support for non-interactive execution.

The program should be able to run non-interactively, in such a way that calls to jkl can be made part of a script. It's currently not the case (AFAIK, calling jkl with a file always call $EDITOR if found).

Moreover, the -f switch should accept - as a way to mean "standard input". And/or we should detect if something is piped to jkl to default to standard input processing.

Automated releases

We should use CI to automatically generate binary and source code releases.

Perhaps I can contribute to this.

Support for moving tasks

It should be possible to move from one sprint to the next and/or to current sprint and/or repriorize within backlog.

Allow configuration to be sourced from hidden folders

Ideally, jkl would allow reading a configuration from .config/jkl. While it is used predominantly for graphical applications, it is a recognized standard configuration file location.

Probably around here the logic could be changed to allow recursing through hidden folders, or specify that .config/jkl/config should be parsed

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.