Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
sbws
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
juga
sbws
Commits
34e566c3
Commit
34e566c3
authored
6 years ago
by
juga
Browse files
Options
Downloads
Patches
Plain Diff
Rephrase timestamps format
parent
2b9b1158
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
CONTRIBUTING.rst
+4
-6
4 additions, 6 deletions
CONTRIBUTING.rst
with
4 additions
and
6 deletions
CONTRIBUTING.rst
+
4
−
6
View file @
34e566c3
...
...
@@ -93,6 +93,10 @@ Before release 1.0.0, some docstrigs do not have 3 double quotes ``"""``
New features should add a corresponding documentation.
Timestamps must be in UTC. It is prefered to use ``datetime`` objects or
Unix timestamps. Timestamps read by the user should be always formatted in
`ISO 8601 <https://en.wikipedia.org/wiki/ISO_8601>`_
Git and GitHub Guidelines
=========================
...
...
@@ -119,12 +123,6 @@ a branch, add a version suffix (for example: "_02").
Coding Guidelines
=================
**Strongly prefer Unix timestamps or datetime objects in UTC** and always
work in UTC for as long as possible. When reading/writing/manipulating results
from some period of time in the past, always err on the side of caution. For
example, open an extra file into the past just in case it happens to include
result lines that have timestamps that are still considered valid (of course,
ignore results in the file that are no longer valid).
**Document your addition, fix, change, or whatever in the changelog**. See
`keep a changelog`_ for the standard we follow. Of note, add Added, Changed,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment