Automating Call To Action Delivery (Repo XP Report)

[0x4007]

We envision that on our upcoming landing page for the XP product, we need to have a call to action that will convince users to pay for the product.

The idea is to have them input a repository URL and then we can send them an XP report of the last month for their team. Ideally this would be in the form of a link to the dashboard so they can see everything.

I imagine that we can leverage the tech from https://github.com/0x4007/travel-stipend/ to trigger a run using text-conversation-rewards https://github.com/ubiquity-os-marketplace/text-conversation-rewards/actions/workflows/compute.yml @gentlementlegen please add any necessary details like what branch its on and how to make this all work together.

Details on running text-conversation-rewards action

• we need to run this securely either through the kernel or calling directly by providing the proper signature
• there should be a way to know if that was previously run on this repo to avoid running it multiple times
• we can ignore private repositories
• at the end of the run, we can send the results via email to the user
• XP is based on priority / rewards combination, we need a way to define what the labels would have been, theoretically

Safety

We must only allow this to work once per organization. This is so they can only get this free report one time. In theory this can be circumvented if they transfer repos to new orgs but that seems like a lot of headache and unlikely for established orgs to do.

[gentlementlegen]

If I understand, the workflow would be:

1. the user click on some generate button in the frontend, with the url to its org
2. this triggers a run of the text-converation-rewards plugin
3. the user can then see the results on the frontend throught some dashboard

The major technical problems I see here is that:

1. users won't have the GitHub App installed, so no way to authenticate
2. so the plugin cannot go through private repositories
3. also the Action can take quite a while to run, I don't see a user refreshing the page for results for an hour
4. XP is based on priority / rewards combination, which these issues won't have, how do we actually compute xp?

[0x4007]

If I understand, the workflow would be:

1. the user click on some generate button in the frontend, with the url to its org
2. this triggers a run of the text-converation-rewards plugin
3. the user can then see the results on the frontend throught some dashboard

The major technical problems I see here is that:

1. users won't have the GitHub App installed, so no way to authenticate

Use a PAT

3. so the plugin cannot go through private repositories

No private repos allowed

5. also the Action can take quite a while to run, I don't see a user refreshing the page for results for an hour

We tell them their report will be ready in about an hour, perhaps we should attempt to email it and CC ourselves.

7. XP is based on priority / rewards combination, which these issues won't have, how do we actually compute xp?

@shiv810 do you think we can estimate their labels with your fine tuned model?

[gentlementlegen]

I guess with a PAT we can log the bot as the user itself. But the signatures wouldn't match to run the plugin however. Also you mentioned only allowing one run per user, so we need to determine a way to store that.

An email sounds fine sure.

[0x4007]

Can you fill out the spec @gentlementlegen

[0x4007]

we need to run this securely either through the kernel or calling directly by providing the proper signature

The tech from 0x4007/travel-stipend is implemented in a prototype I'm working on now for direct artifact reads. The capability also supports dispatches from UI.

there should be a way to know if that was previously run on this repo to avoid running it multiple times

In the landing page (specifically the call-to-action's endpoint) we can have a Deno KV store for this. It can check the KV store prior to dispatching.

we can ignore private repositories
at the end of the run, we can send the results via email to the user

Figure out how to email the user directly from within the GitHub Action. Seems simplest.

XP is based on priority / rewards combination, we need a way to define what the labels would have been, theoretically

@shiv810 is working on a tool now for exactly this.

[ubiquity-os]

Note

The following contributors may be suitable for this task:

gentlementlegen

75% Match ubiquity-os-marketplace/text-conversation-rewards#315

[0x4007]

[!NOTE]
The following contributors may be suitable for this task:

gentlementlegen

75% Match ubiquity-os-marketplace/text-conversation-rewards#315

I guess it would make sense to have a UI that lists which we are recommended to take from high match to low. 100%-80% as an intermediary step to the OS actively managing our sprints with buffers and moving tasks around based on priority and our capacity.