Martin Günther mintar

## GitCommitBestPractices.md

      
              2 files
            
          
              70 forks
            
          
              20 comments
            
          
              323 stars
            
          
                luismts
                / GitCommitBestPractices.md
            
            
              Last active
              May 7, 2024 09:43
            
              
                Git Tips and Git Commit Best Practices
              
          
    Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong.
With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

  
## markdown-details-collapsible.md

      
              1 file
            
          
              165 forks
            
          
              184 comments
            
          
              1302 stars
            
          
                pierrejoubert73
                / markdown-details-collapsible.md
            
            
              Last active
              May 8, 2024 10:42
            
              
                How to add a collapsible section in markdown.
              
          
    How to add a collapsible section in markdown

1. Example


  Click me
Heading


Foo
Bar

Baz


Qux


## Repository Maintenance Levels.md

      
              1 file
            
          
              1 fork
            
          
              7 comments
            
          
              57 stars
            
          
                cheerfulstoic
                / Repository Maintenance Levels.md
            
            
              Last active
              May 8, 2024 15:52
            
              
                Repository Maintenance Levels
              
          
    After reading Why I'm Frequently Absent from Open Source by James Long and listening the corresponding The Changelog episode, I dwelt on the idea and believe that open source maintainers...

... should never be ashamed if they don't have time for a project.
... should be honest with themselves and open with their users so that everybody can be on the same page
... are people and they have at one time or another responsibilities or hardships that they need to attend to which reasonably take them away from a project
... may also reasonbly decide that they don't like the direction of a project or that they would like to explore other things and may leave a project permanently.

Along this line of thinking I've created a set of descriptions for different levels at which a project might be maintained. A maintainer can use these to announce to their users the current ability that they have to dedicate to a pr

  
## plot_controller.py
#!/usr/bin/env python
import actionlib
from control_msgs.msg import (
    FollowJointTrajectoryAction,
    FollowJointTrajectoryGoal,
    FollowJointTrajectoryActionGoal,
    FollowJointTrajectoryResult,
    JointTrajectoryControllerState)
import matplotlib.pyplot as plt
import matplotlib.animation as animation
	#!/usr/bin/env python
	import actionlib
	from control_msgs.msg import (
	FollowJointTrajectoryAction,
	FollowJointTrajectoryGoal,
	FollowJointTrajectoryActionGoal,
	FollowJointTrajectoryResult,
	JointTrajectoryControllerState)
	import matplotlib.pyplot as plt
	import matplotlib.animation as animation