Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / druths/xp issues and pull requests
#23 - Switched scripts to console_scripts
Pull Request -
State: closed - Opened by druths over 3 years ago
#22 - Make script installed directly from setup.py
Issue -
State: closed - Opened by druths over 3 years ago
Labels: enhancement
#21 - Migrate file format to yml
Issue -
State: open - Opened by druths over 3 years ago
Labels: enhancement
#20 - Output for a task should be cached
Issue -
State: open - Opened by druths over 7 years ago
Labels: enhancement
#19 - Fixes #18
Pull Request -
State: closed - Opened by hardik-vala about 8 years ago
- 1 comment
#18 - Optionally omitting the .xp extension when using a pipeline
Issue -
State: closed - Opened by hardik-vala about 8 years ago
#17 - Stack traces in code blocks don't reference the right pipeline or line numbers
Issue -
State: open - Opened by druths about 8 years ago
Labels: enhancement
#16 - Updated the cluster example in the README
Pull Request -
State: closed - Opened by hardik-vala about 8 years ago
#15 - Using a variable from another pipeline
Issue -
State: closed - Opened by hardik-vala about 8 years ago
- 6 comments
#14 - Fixes #13
Pull Request -
State: closed - Opened by hardik-vala about 8 years ago
#13 - $PLN($MY_CONST) error
Issue -
State: closed - Opened by hardik-vala about 8 years ago
- 1 comment
#12 - Specifying file encoding
Issue -
State: open - Opened by hardik-vala about 8 years ago
- 3 comments
Labels: question
#11 - Uninstalling flex
Issue -
State: closed - Opened by hardik-vala over 8 years ago
- 2 comments
#10 - world_pop is an empty example
Issue -
State: closed - Opened by filipstachura over 8 years ago
- 2 comments
#9 - Don't create output data folder for pipelines with no output data (?)
Issue -
State: open - Opened by hardik-vala over 8 years ago
- 3 comments
#8 - Flex name conflicts with GNU Flex
Issue -
State: closed - Opened by sjackman over 8 years ago
- 2 comments
#7 - Have some way of easily flagging a task as being forced
Issue -
State: closed - Opened by druths over 8 years ago
- 1 comment
Labels: enhancement
#6 - In multi-line comment inside task, empty lines trigger a parse error
Issue -
State: open - Opened by druths over 8 years ago
Labels: bug
#5 - Updated README
Pull Request -
State: closed - Opened by hardik-vala over 8 years ago
- 1 comment
#4 - Corrected mark usage
Pull Request -
State: closed - Opened by hardik-vala over 8 years ago
- 1 comment
#3 - When a task doesn't exist (but is specified), tasks should be suggested
Issue -
State: open - Opened by druths about 9 years ago
Labels: enhancement
#2 - If a task is run, but has already been marked, an error should be printed to notify the user that nothing was done.
Issue -
State: closed - Opened by druths about 9 years ago
Labels: bug, enhancement
#1 - In the run subcommand, when a task doesn't exist, an exception is thrown (appears to be a wrong variable tname)
Issue -
State: closed - Opened by druths about 9 years ago
- 1 comment
Labels: bug