Generalized "GitHub Webhook + Contributor Role -> Rewards" No Config v1

[0x4007]

Dynamically map the config property name to count the amount of matching webhook events that occur in the issue/pull timeline, and credit accordingly. In which case, this plugin seems generally useful for mapping any value to any event, in the context of an issue or pull!

All this is intended to do is:

1. get the timeline of events from the issue and the linked pulls
2. assign a value of 1 to every event that is counted, per contributor.
3. return sum totals.

In the next iteration, we should identify the user's "class" (specification author, assignee, collaborator, contributor)

In the final iteration, we should enable config.

• All webhook events reference.

[0x4007]

301 based on a very quick Look

[Amit0617]

/start

[ubiquity-os]

! Please set your wallet address with the /wallet command first and try again.

[Amit0617]

/wallet 0x47c0C4eb25b0Aa4bC5D1E6341F5eE9A6aD2B596c

[ubiquity-os]

+ Successfully registered wallet address

[Amit0617]

/start

[ubiquity-os]

Deadline	Fri, Oct 11, 7:06 AM UTC
Beneficiary	0x47c0C4eb25b0Aa4bC5D1E6341F5eE9A6aD2B596c

Tip

• Use /wallet 0x0000...0000 if you want to update your registered payment wallet address.
• Be sure to open a draft pull request as soon as possible to communicate updates on your progress.
• Be sure to provide timely updates to us when requested, or you will be automatically unassigned from the task.

[Amit0617]

Wanted to be sure about how the pull request is supposed to be created? Should I create a new folder with all files, since there are probably going to be multiple plugins here?

[0x4007]

It should be one plugin. Fork the plugin template and link your pull here

[Amit0617]

@0x4007 may I ask for reviewing above PR?

[0x4007]

It's closed because you didn't follow the necessary instructions

[Amit0617]

I was asking to review the one opened after the closed one (following instructions as suggested). Amit0617/contributor-rewards#3 particularly

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

It's up for review.

[gentlementlegen]

@kingsley-einstein Your PR seems to target your own repo somehow, I cannot assign reviewers there.

[kingsley-einstein]

@kingsley-einstein Your PR seems to target your own repo somehow, I cannot assign reviewers there.

@gentlementlegen
It was forked from the template repo, and I'm not supposed to raise a PR against that repo.

[gentlementlegen]

It doesn't make sense, your PR should be opened against Ubiquity's organization, there should be a repo that would accommodate your changes. If there is none at the moment ask for one to be created.

[kingsley-einstein]

It doesn't make sense, your PR should be opened against Ubiquity's organization, there should be a repo that would accommodate your changes. If there is none at the moment ask for one to be created.

@gentlementlegen I know that now. Could one be created now, so I switch origins locally, and commit my changes?

[EresDev]

You can test directly against the relevant PR, by running the slash command "/scan-contributions". For the env vars, you'll mostly need GITHUB_TOKEN set in a .dev.vars file.

I tried adding github token, but the issues are still there.

It turned out manifest file isn't being served correctly but the plugin should work smoothly with ubuiquity-os-kernel instances. I fixed manifest file issue and then the event being passed is null. So, it needs some attention to work smoothly with kernel as plugins are supposed to. Maybe try setting up a local instance to debug? Testing it only in your PR is helpful but it isn't sufficient.

[kingsley-einstein]

You can test directly against the relevant PR, by running the slash command "/scan-contributions". For the env vars, you'll mostly need GITHUB_TOKEN set in a .dev.vars file.

I tried adding github token, but the issues are still there.

It turned out manifest file isn't being served correctly but the plugin should work smoothly with ubuiquity-os-kernel instances. I fixed manifest file issue and then the event being passed is null. So, it needs some attention to work smoothly with kernel as plugins are supposed to. Maybe try setting up a local instance to debug? Testing it only in your PR is helpful but it isn't sufficient.

@EresDev
The task relies on just listening for issue comments, not all kinds of events. Also, to get it to work, you must send a payload with the same structure as Github event payloads.

[EresDev]

The task relies on just listening for issue comments, not all kinds of events.

Yes, the event I am trying is issue_comment.created and it is having problems in processing it.. The event is passed from github, so yes it is a real GitHub event payload. Only difference from your setup is that I have kernel, and plugin running on my local machine. I am testing here.

[Keyrxng]

@0x4007 @gentlementlegen @EresDev

I already built this plugin and met the targets of each spec for the whole parent task including unit tests.

The org repo was deleted and my PR along with it for some reason before the task was broken into four steps.

I'd like to submit my plugin for consideration for these tasks considering I already put in the work and the PR was received well at the time and is ready to go.

1. This plugin would sooner be live.
2. My efforts would not have gone to waste and no-one need waste any more of theirs unnecessarily (both reviewers and contributors)

[0x4007]

@0x4007 @gentlementlegen @EresDev

I already built this plugin and met the targets of each spec for the whole parent task including unit tests.

The org repo was deleted and my PR along with it for some reason before the task was broken into four steps.

I'd like to submit my plugin for consideration for these tasks considering I already put in the work and the PR was received well at the time and is ready to go.

1. This plugin would sooner be live.

2. My efforts would not have gone to waste and no-one need waste any more of theirs unnecessarily (both reviewers and contributors)

If it works according to the spec and you can prove it then sure. Although we would probably need to recreate the issue because a lot of conversation that doesn't belong under the issue happened here.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

It's under review

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

Still under review botty.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

Still under review botty! Sheesh!

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

Still under review.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

under review

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

under review

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

under review

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[ubiquity-os-beta]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

[kingsley-einstein]

@kingsley-einstein, this task has been idle for a while. Please provide an update.

Still under review