Detect PR & Auto Assign Issue

[0x4007]

It would be nice if the bot can detect open pull requests to unassigned issues and automatically assign the pull request author.

Make sure that it only works for the first pull request opened and it's actively being worked on. In case two bounty hunters try to compete with each other on the bounty without first assigning themselves: the first to open should get the assignment.

https://t.me/UbiquityDevPool/2506

[seprintour]

/start

[ubiquibot]

@seprintour The time limit for this bounty is on Thu, 27 Apr 2023 13:39:05 GMT

Your currently set address is:
0x3623338046b101ecEc741De9C3594CC2176f39E5
please use /wallet 0x4FDE...BA18 if you want to update it.

[seprintour]

Unfortunately, pull requests linked to an issue by comments does not show up on the pull request and issues endpoint

[seprintour]

However, i found it shows up on the timeline here as a cross-reference

Either this or scraping pull requests to look for open pull requests on the Development tab should work

[seprintour]

If anyone has a solution to show issues on a pull request or vice versa, it would appreciated.

As the current implementation i have would require :- Fetching all PRs, Fetching all open issues, Checking timelines of open requests and if there is the pull request on the timeline exists, is open and no one is assigned

Owner of pull request is assigned

[Steveantor]

If anyone has a solution to show issues on a pull request or vice versa, it would appreciated.

As the current implementation i have would require :- Fetching all PRs, Fetching all open issues, Checking timelines of open requests and if there is the pull request on the timeline exists, is open and no one is assigned

Owner of pull request is assigned

You shouldn't assign yourself without fully understanding the issue or possible implementation first.

[seprintour]

If anyone has a solution to show issues on a pull request or vice versa, it would appreciated.
As the current implementation i have would require :- Fetching all PRs, Fetching all open issues, Checking timelines of open requests and if there is the pull request on the timeline exists, is open and no one is assigned
Owner of pull request is assigned

You shouldn't assign yourself without fully understanding the issue or possible implementation first.

I understood it and it is in progress.. just need to confirm, you can see i have possible implementations above lol

Just need to know what would work best

[seprintour]

So i have 3 possible :- scraping, using timelines or pull requests body.. I initially thought GitHub API will add the issue on the pull request linked through the body.

But they don't, that's why i'm here

[Steveantor]

So i have 3 possible :- scraping, using timelines or pull requests body.. I initially thought GitHub API will add the issue on the pull request linked through the body.

But they don't, that's why i'm here

imo, scraping is the way to go since GitHub doesn't provide any API.
you should parse linked element (like below) instead of Resolves ##

modify the src/helpers/parser.ts as needed.

[seprintour]

However, i found it shows up on the timeline here as a cross-reference

Either this or scraping pull requests to look for open pull requests on the Development tab should work

Thanks for the file parser.ts, works exactly as i planned here.. would have to look at the Development tab for mine

[seprintour]

@Steveantor scraping was a breeze.. i have finalised the PR and its ready to review

Thanks for your help again

[ubiquibot]

[ CLAIM 100 DAI ]

0x3623338...176f39E5

[ubiquibot]

@seprintour please be sure to review this conversation and implement any necessary fixes. Unless this is closed as completed, its payment of 100.0 DAI will be deducted from your next bounty.

[ubiquibot]

@seprintour - Releasing the bounty back to dev pool because the allocated duration already ended!
Last activity time: Thu Apr 27 2023 09:41:53 GMT+0000 (Coordinated Universal Time)

[0x4007]

This isn't working anymore. #746

Perhaps a core team member should take this over.

rfc @ubiquity/software-development

@wannacfuture can you investigate this

---

Here is the diff from the latest commit on this pull request to the current development HEAD: https://github.com/ubiquity/ubiquibot/compare/2399857f507467fa9f9672855580c68c457bee97..development#diff-41f183deca0c54367420ce6e3bf0764513ba00c2ce136bb19056c616c2c06a59

Useful to compare against the changed files for this feature https://github.com/ubiquity/ubiquibot/pull/273/files

[seprintour]

This isn't working anymore.

Perhaps we'd need tests here, so one doesn't work on one feature and break another.

Every feature in the bot would be tested

[wannacfuture]

This isn't working anymore. #746

Perhaps a core team member should take this over.

rfc @ubiquity/software-development

@wannacfuture can you investigate this

Here is the diff from the latest commit on this pull request to the current development HEAD: https://github.com/ubiquity/ubiquibot/compare/2399857f507467fa9f9672855580c68c457bee97..development#diff-41f183deca0c54367420ce6e3bf0764513ba00c2ce136bb19056c616c2c06a59

Useful to compare against the changed files for this feature https://github.com/ubiquity/ubiquibot/pull/273/files

Let me take a look at this.

[seprintour]

@pavlovcik i noticed this is a penalty.. It's been a long time since I worked on this issue

[0x4007]

@pavlovcik i noticed this is a penalty.. It's been a long time since I worked on this issue

Let's see if the penalty feature even works...I've never seen it work in production before. If it does, I'll make up for the difference. Just let me know the results please!

[seprintour]

@pavlovcik i noticed this is a penalty.. It's been a long time since I worked on this issue

Just let me know the results please!

Okay, I'd do that. Perhaps my next permit would contain the penalty info

[0x4007]

As a heads up: if it renders a permit with a penalty don't claim it. I'll manually revoke the permit, remove the penalty, and regenerate the new permit instead.

[wannacfuture]

Just want to make it clear.

So, @pavlovcik We'll ignore all the assign rules for the linked first pull request for the issue, right?
'll assign that pr's author to the issue even he reached max limit or so.

[Steveantor]

Just want to make it clear.

So, @pavlovcik We'll ignore all the assign rules for the linked first pull request for the issue, right? 'll assign that pr's author to the issue even he reached max limit or so.

Not ignoring will render the PR author's contribution useless, and other users will simply copy-paste his code
and take the reward

[0x4007]

Just want to make it clear.

So, @pavlovcik We'll ignore all the assign rules for the linked first pull request for the issue, right? 'll assign that pr's author to the issue even he reached max limit or so.

I designed the rules for reasons. Always follow the rules.

[wannacfuture]

I took a look on it.

necessary functions are ready on #657

'll finish this right after it is merged.