Comments

• 

  almost 6 years ago by zhangxiaofei | Reply

  The first version of git snitch was done successfully and has been up and sending emails about upstream commits which may worth backporting to SLE to a small number of interested people whenever it finds a new commit containing predefined keywords. However..

  • It is written in bash and not maintenance friendly
  • The configuration is in a /etc/passwd -like format with inadequate extensibilities when if we want to configure for multiple users, snitching different sets of git repositories, with different sets of keywords being notified on different time intervals, each settings may involve predefined global settings with different blacklists/whitelists, etc.
  • The recurring are set in cronjob without customization for each user
  • There are flaws in the keyword regex matching

  So I plan to rewrite it..

  • In python which is more readable and parses yaml with more easy so as to..
  • Put the configurations into yaml
  • Move the recurring from cronjob into the configuration
  • Make smarter keyword matching

  Other possible ideas:

  • Automatically send snitched commits as cards to a Trello board
    • Which will be hard without human interference as the current results contains majority of commits irrelevant to SLE15

×
Edit Comment 3226
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
The first version of git snitch was done successfully and has been up and sending emails about upstream commits which may worth backporting to SLE to a small number of interested people whenever it finds a new commit containing predefined keywords. However.. * It is written in bash and not maintenance friendly * The configuration is in a /etc/passwd -like format with inadequate extensibilities when if we want to configure for multiple users, snitching different sets of git repositories, with different sets of keywords being notified on different time intervals, each settings may involve predefined global settings with different blacklists/whitelists, etc. * The recurring are set in cronjob without customization for each user * There are flaws in the keyword regex matching So I plan to rewrite it.. * In python which is more readable and parses yaml with more easy so as to.. * Put the configurations into yaml * Move the recurring from cronjob into the configuration * Make smarter keyword matching Other possible ideas: * Automatically send snitched commits as cards to a Trello board * Which will be hard without human interference as the current results contains majority of commits irrelevant to SLE15
 
×
Reply to zhangxiaofei
The first version of git snitch was done successfully and has been up and sending emails about upstream commits which may worth backporting to SLE to a small number of interested people whenever it finds a new commit containing predefined keywords. However..
• It is written in bash and not maintenance friendly
• The configuration is in a /etc/passwd -like format with inadequate extensibilities when if we want to configure for multiple users, snitching different sets of git repositories, with different sets of keywords being notified on different time intervals, each settings may involve predefined global settings with different blacklists/whitelists, etc.
• The recurring are set in cronjob without customization for each user
• There are flaws in the keyword regex matching
So I plan to rewrite it..
• In python which is more readable and parses yaml with more easy so as to..
• Put the configurations into yaml
• Move the recurring from cronjob into the configuration
• Make smarter keyword matching
Other possible ideas:
• Automatically send snitched commits as cards to a Trello board
  • Which will be hard without human interference as the current results contains majority of commits irrelevant to SLE15
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

This is an [example link](http://example.com/)

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview