-
-
Notifications
You must be signed in to change notification settings - Fork 266
Conversation
Great idea! Suggestions:
|
Not sure it that's worth the trouble. Better discuss why we need unusual branch names before implementing this. |
I propose to count how many times a branch is used and if it is bellow a percentage, it is unusual. Hide the unususal branches or display them outside of the table in a section for them. That way we know that there are some branches that should not be there. That way, only branches from 6.0 onward are shown. I might even move 6.0 to a table lower down the output. Master should get its own section, since we don't want addon repos to have a master, but we want meta repos such as this one to have one. |
I was wondering about this, would it be a good idea to also include a setup.py? I will also add a readme |
Maybe a setup.py would be an overkill. If you're adding a README, maybe a requirements.txt for a couple of dependencies is also a overkill: just give the installation instructions on the README. |
Well, I like requirements.txt because you can do |
@bwrsandman can you label this as a WIP? |
good idea. |
I know this sounds like offloading my work, but if anyone wants to use this, I made a checklist for contributions. I will eventually get to this, but I am in a bit of a rush at the moment. |
@bwrsandman I see open Issues as something waiting for an action. Since the discussion has ended here, could we close this until someone has more to add on it? |
Closing this for now, since no actions are required at the moment. |
52efeb0
to
9fa0b28
Compare
Any suggestions what to put into the README.md? |
@bwrsandman I think the contents of your initial comment describing what this does and its output would fill up a README quite nicely. It sums up what it does and how to use it. |
That's a great initiative @bwrsandman (that I missed until you mentioned it this week). Great, thanks! For the record, our sysadmin colleagues work on many puppet modules, and have a dashboard as well. Their use case is a bit different, because repositories are owned by the company, and the dashboard shows also private ones if they are visible with your github token. The dashboard: http://puppet.camptocamp.net/modules Code: https://github.com/camptocamp/github-repositories-dashboard |
@bwrsandman Is this intended to be a helper script? Should it go in |
Got an error when testing:
|
@dreispt what version of progressbar are you using? |
progressbar (2.3) |
Example usage: ```bash pip install -r requirements.txt ./generate_control_board.py -u bwrsandman -O OCA -o badges.md -x gh-pages ```
It works with progressbar 2.2, I am looking at 2.3 now. There was a big change between these versions. |
665475f
to
18ffdc9
Compare
Move PR to OCA/maintainer-tools#71 |
method readfp
Proposal for a script which will display in markdown the travis and coverage status of all branches in OCA.
TODO:
requirements.txt
README.md
The aim is to put the output in a readme of this project to display the following:
Good branch names
OCA repo quality control board
Odd branch names
OCA repo quality control board