issues
search
spacetelescope
/
style-guides
An opinionated guide on how we work.
Creative Commons Attribution 4.0 International
55
stars
33
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Adopt the Scientific Python Developers Guide
#122
WilliamJamieson
opened
1 year ago
0
Notebook accessibility from Scipy 2023
#121
pllim
opened
1 year ago
0
Update Master Branch
#120
catherine-martlin
opened
1 year ago
0
Remove pytest-openfiles from recommended Python testing tools
#119
pllim
opened
1 year ago
0
Updated community version support to include Astropy policy link
#118
tddesjardins
closed
1 year ago
0
use canonical filename of RTD configuration
#117
zacharyburnett
closed
2 years ago
0
"such as" repeated
#116
falkben
closed
3 years ago
2
Add a clarification that narrative docs should have context
#115
eteq
closed
3 years ago
0
MNT: Update package template instructions
#114
pllim
closed
3 years ago
0
TST: Replace Travis
#113
pllim
closed
3 years ago
0
Ditch Travis CI as a recommended solution
#112
pllim
closed
3 years ago
4
Add section about PyPI publication service
#111
rendinam
closed
3 years ago
0
Jupyter notebook style guide revision
#110
lglattly
closed
3 years ago
9
Redirector instructions
#109
bhayden53
closed
4 years ago
0
Add "Branching" workflow to git workflow guide
#108
bourque
closed
4 years ago
7
Create ROADMAP.md
#107
arfon
closed
2 years ago
1
Create a ROADMAP
#106
pllim
opened
4 years ago
0
Organize a hack day in 2020
#105
pllim
closed
1 year ago
1
Update python packaging information
#104
stscicrawford
closed
3 years ago
0
Distribute flyers around STScI
#103
pllim
closed
1 year ago
1
Badge for packages that follow style guide
#102
pllim
opened
4 years ago
2
Present this in TIPS and EngOps in 2020
#101
pllim
closed
1 year ago
1
This thing needs to be managed and advertised
#100
pllim
closed
4 years ago
2
Spell checker modifications
#99
sean-lockwood
closed
4 years ago
1
Redirector instructions
#98
bhayden53
closed
4 years ago
1
Update security.md
#97
stscicrawford
closed
5 years ago
0
Detailed Zenodo instructions for new software DOI?
#96
pllim
opened
5 years ago
1
Community Name for Zenodo Software DOI?
#95
pllim
closed
5 years ago
1
Adding example notebook and instructions for how to implement footer.
#94
arfon
closed
5 years ago
3
Review security style guide
#93
stscicrawford
opened
5 years ago
2
Notebook style guide: Footer instruction confusing
#92
pllim
closed
5 years ago
1
Fix deps instructions typo
#91
pllim
closed
5 years ago
1
Description of how to cite the software
#90
brechmos-stsci
closed
5 years ago
9
Add information about how to cite software
#89
brechmos-stsci
closed
5 years ago
1
Fix two typos
#88
larrybradley
closed
5 years ago
0
Testing style guide: Discourage Travis CI, find replacement?
#87
pllim
closed
5 years ago
2
Microservices style guide
#86
stscicrawford
opened
5 years ago
1
Test code coverage discussion (Codecov vs Coveralls)
#85
brechmos-stsci
closed
5 years ago
1
Add astroconda to release guide
#84
stscicrawford
closed
3 years ago
0
DOI for each release of our public software
#83
brechmos-stsci
closed
5 years ago
13
Update readme links
#82
eteq
closed
5 years ago
0
Web style guide should link to branding page
#81
eteq
opened
5 years ago
0
Added in issue and pr example tempates
#80
brechmos-stsci
closed
5 years ago
12
Updated text on dependency versions
#79
brechmos-stsci
closed
5 years ago
3
Use github pages for this repo
#78
eteq
opened
5 years ago
1
Added information about Box
#77
brechmos-stsci
closed
5 years ago
3
Adding link to 12-factor config document
#76
arfon
closed
5 years ago
0
Notebook guide suggestions
#75
eteq
opened
5 years ago
0
PR review guide (aka "Code Review")
#74
brechmos-stsci
closed
5 years ago
7
Style guide for code contributors?
#73
pllim
closed
4 years ago
4
Next