issues
search
canonical
/
is-charms-contributing-guide
The code contributing guide for the IS charms team
Apache License 2.0
2
stars
1
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add index and standard for charm configuration option description
#29
amandahla
closed
1 year ago
0
add guidance on picking dependencies
#28
jdkandersson
closed
1 year ago
1
add docstring example
#27
jdkandersson
closed
1 year ago
0
Docstring example
#26
jdkandersson
closed
1 year ago
0
add expected static code analysis tools
#25
jdkandersson
closed
1 year ago
0
add standard for type hints
#24
jdkandersson
closed
1 year ago
1
add clarification to the test structure for long descriptions
#23
jdkandersson
closed
1 year ago
0
add standard for docstrings
#22
jdkandersson
closed
1 year ago
1
Pinning dependency versions
#21
jdkandersson
opened
2 years ago
0
Include a changlog in the repositories
#20
jdkandersson
opened
2 years ago
1
add codeowners file
#19
jdkandersson
closed
2 years ago
0
Add codeowners specification
#18
arturo-seijas
closed
2 years ago
0
add standard for f-strings and log message formatting
#17
jdkandersson
closed
2 years ago
0
Automatically add reviewers to PRs
#16
arturo-seijas
closed
2 years ago
1
add check and bypassing rules guide
#15
jdkandersson
closed
2 years ago
0
add standard for repository setup
#14
jdkandersson
closed
2 years ago
0
Don't use f-strings in log messages
#13
jdkandersson
closed
2 years ago
1
GitHub Repo Setup
#12
jdkandersson
closed
2 years ago
1
Type hints
#11
jdkandersson
closed
1 year ago
1
Docstring format
#10
jdkandersson
closed
1 year ago
0
Add test coverage standard
#9
jdkandersson
closed
2 years ago
0
Add standard for the Ubuntu and Python version
#8
jdkandersson
closed
2 years ago
0
Import module rather than from module
#7
jdkandersson
closed
2 years ago
8
Code coverage standard
#6
jdkandersson
closed
2 years ago
9
Standard for pre-commit hooks
#5
jdkandersson
closed
1 year ago
2
Standard for checking error/ log messages
#4
jdkandersson
opened
2 years ago
2
add standard on how to deal with code that does not comply with standards
#3
jdkandersson
closed
2 years ago
0
add standard for structuring tests
#2
jdkandersson
closed
2 years ago
0
add standard for the programming language to be used
#1
jdkandersson
closed
2 years ago
4
Previous