auto-update repos' README? about libgrabber

[jimaek]

Too spammy. How about opening an Issue in this same repo or in jsdelivr/jsdelivr and mentioning the author? This way he gets a notifications and will come and check out the issue.

Which will contain info about jsDelivr and that his project is now auto-updated.

[tomByrer]

Too spammy.

Sorry, I didn't explain well. I was thinking of doing this ONLY the first time libgrabber is ran. That's why if "CDN" or "jsDelivr" is in the README already, then no PR is made. The README PR is only a service to help add instructions, like I do in real life.
Or do you think that is too spammy also? (I understand if you do)

How about opening an Issue in this same repo or in jsdelivr/jsdelivr and mentioning the author?

Neat idea... maybe as an option in the Update.json; "update notification": "none"(default)|"issue me"|"issue jsdelivr"|"email"|"twitter"?

[jimaek]

Yeah, I was talking about the first time as well. The first time notify the author by mentioning them in an issue. Most authors wont appreciate an automated PR.

The update notification option is interesting. @aleksandara What do you think?

[tomByrer]

Most authors won't appreciate an automated PR.

Understandably. I guess README instructions will have to be an educational issue then.

I'm starting to warm up to an opt-in Twitter notification. Could add a link to the jsDeliver.com/!#PROJECT slug in the post. & if we could get their "changes" URL (usually CHANGELOG.*, or README.md#changes, then it would be a service for them; they get some automated public relations/social SEO as well.

[jimaek]

The problem is the rate-limiting by Twitter. No more than a few tweets can go out in a day. And if we wait 1-2 days to notify the author then the point of the notification is lost.

[aleksandara]

I like the idea of notifying developer when an update is done, at least for the first time. When the developer's username is mentioned in the PR libgrabber creates, we can then display in the PR information to do a quick check for a missing file, how to change update.json, provide some links, etc.

Maybe we add additonally an option in update.json to choose when to send an update. E.g. always, major (when major part of version changes), minor, etc.

Btw, in "update notification" option, what is the difference between issue me and issue jsdelivr?

[jimaek]

Yeah, for now we can mention the author in the PR the bot opens. I forgot about that completely.
I think its the most optimal solution.

[tomByrer]

issue me = post an issue to the repo's issue tracker; best for "Please update your README & let your twitter followers know" reminder.
issue jsdelivr = @author inside jsdelivr's PR; exactly jimaek's idea; best for gentle poking

I like the prompt for fixing libgrabber issues.

rate-limiting by Twitter. No more than a few tweets can go out in a day

Sure about that? Seems to be a bit more, & I assume only a fraction will turn on Tweet notifications. I Twit only 1/week, so never hit it ;) Could just use it for new projects at first to test out.

[jimaek]

@aleksandara Currently if enable the author notification does it notify him only once or on every update?