Skip to content

Issues: russHyde/data_buddy

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

16 Open 37 Closed
16 Open 37 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Automatic documenting of local R packages?
#92 opened Apr 7, 2020 by russHyde
Use .yaml to specify subjob order, and push subjob-setup code into buddy 02 : structure Suggested restructuring / refactoring to improve the code / directories
#89 opened Oct 23, 2019 by russHyde
Use relative path to subjobs in .sidekick/setup/subjob_names.txt 02 : structure Suggested restructuring / refactoring to improve the code / directories
#88 opened Oct 23, 2019 by russHyde
"subjob_names" should be called "subjob_order" 02 : structure Suggested restructuring / refactoring to improve the code / directories
#72 opened Apr 10, 2019 by russHyde
set -euo pipefail in job_specific_vars.sh 01 : feature New feature or request
#71 opened Apr 10, 2019 by russHyde
links to links 04 : bug Something isn't working
#70 opened Apr 10, 2019 by russHyde
initial conda-env requirements for data_buddy
#68 opened Apr 10, 2019 by russHyde
4
allow subjobs with no sidekick/buddy present 01 : feature New feature or request
#67 opened Apr 10, 2019 by russHyde
Recursive .sidekick validate? 01 : feature New feature or request 13 : sidekick Relevant to `sidekick` scripts and config
#61 opened Apr 9, 2019 by russHyde
add ./sidekick run <...args...> for running a project 01 : feature New feature or request 13 : sidekick Relevant to `sidekick` scripts and config
#37 opened Feb 7, 2019 by russHyde
User shouldn't be prompted for an R package name if they aren't going to make an R package 01 : feature New feature or request 11 : cookie Relevant to the cookie-cutter setup steps
#23 opened Jan 18, 2019 by russHyde
Reinstall buddy if it has been updated since installation 01 : feature New feature or request 13 : sidekick Relevant to `sidekick` scripts and config
#20 opened Jan 18, 2019 by russHyde
validity check the project_name 01 : feature New feature or request 11 : cookie Relevant to the cookie-cutter setup steps
#14 opened Jan 11, 2019 by russHyde
use cookiecutter logic to specify optional files 01 : feature New feature or request 11 : cookie Relevant to the cookie-cutter setup steps
#12 opened Jan 11, 2019 by russHyde
allow user specified build/installation order for R packages 01 : feature New feature or request 13 : sidekick Relevant to `sidekick` scripts and config
#10 opened Jan 10, 2019 by russHyde
2
rename since there is a project_buddy and a data_buddy already in existence 02 : structure Suggested restructuring / refactoring to improve the code / directories
#1 opened Dec 7, 2018 by russHyde
2
ProTip! Adding no:label will show everything without a label.