add function to import PR into entries

[anitanh]

fix #1128

This PR:

• Added function to fetched PRs from github
• Added modal in version detail view to import PRs from github
• Added form validation

Note:

• On deployment we need github token so that we can have request to github API up until 5000 request per hour, without this token we only have 60 requests per hour
• for rate limiting, see: https://developer.github.com/v3/#rate-limiting.
• to set up github token see: https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line#creating-a-token

How to use

1. Click on the github icon on the right side of the page, it will open a pop up to import the PRs.
2. The repository url is filled automatically but should you like to import the PR from another repository you can fill it here too (required).
3. Wait until the label options is rendered.
4. Select the label of which you want to import the PR, if you select more than one label it will only fetch the PR containing all of the selected labels.
5. Select the state of the PR, it can be open or closed or both, if you don't select any it will fetch all PR regardless open or closed.
6. Select a category where the new entries will be associated to (required).
7. Click import, it will begin fetching your PRs and rendering them into entries.

[anitanh]

Travis error is unrelated to this PR

[dimasciput]

Hi @Ann26 , shouldn't this be like an automated process? User doesn't need to do this manually, instead when there is a new PR with specific label, it will create an entry in changelog?
What do you think @timlinux ?

[timlinux]

Hi @Ann26 and @dimasciput

I'm OK with it being a manual process for now but there are a few more things maybe I missed to mention in the original ticket:

We need to be able to specify a time box or at least a starting point so that we don't fetch PR's from before the current release cycle.

It's not clear from your GIF but do you bring image references through?

Do we have logic in place to prevent duplicate entries?

Ideally in the future ,yes, I would like the process to be automated, with the options you provide in the dialog moved into the project properties page so that any new incomiing PR's get added to the latest current changelog. We need a flag to mark a version 'open' or 'closed' to indicate whether new entries may be added to the latest changelog. I would keep the manual tool around too.

[anitanh]

hi @timlinux

It's not clear from your GIF but do you bring image references through?

by image references do you mean the image in the PR? yes it will be in the entries too.

Do we have logic in place to prevent duplicate entries?

No, but if we want to create one, how do we determine that it is a duplicate? If it is the title, I think it is possible to have the same title and yet different PR e.g. update on feature etc

We need to be able to specify a time box or at least a starting point so that we don't fetch PR's from before the current release cycle.

I will add the time box

[timlinux]

No, but if we want to create one, how do we determine that it is a duplicate? If it is the title, I think it is possible to have the same title and yet different PR e.g. update on feature etc

Simply having the same PR url - can you add a PR url field to then entry model for this purpose:

[anitanh]

@timlinux ah okay, I will do, I will create a separate PR with the time constraints and duplicate handler later