feat: add support for custom pull request template paths

[ndom91]

☕️ Reasoning

• After a user comment on discord and some research, it turns out that folks put their PR templates at both .github/PULL_REQUEST_TEMPLATE.md and .github/pull_request_template.md about 50/50. There is also technically an option for folks to put their template anywhere under .github/PULL_REQUEST_TEMPLATE/*.md
• Therefore, adding a settings path for folks to customize which PR template they want to be used.

🧢 Changes

• The PR template enable boolean and PR template path (new) are now in the project preferences.
• This section is hidden if the user is not logged into GitHub

📺 Screenshots

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gitbutler-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 4, 2024 0:46am

[mtsgrd]

About the pre-styled message, look for showToast(...) instead of using showError if you want to render it differently!

[ndom91]

About the pre-styled message, look for showToast(...) instead of using showError if you want to render it differently!

Yeah i tried that initially, but the message still seemed to get rendered into what was displayed as like a <pre /> element.

EDIT: Ahh I see, since the type: 'error' it'll always wrap the content in a <code />. Maybe I'll just make this style: 'neutral' then.

[mtsgrd]

Actually, I was the one confused. I see we use <code> for errors, and markdown formatted content for other content.

[ndom91]

Much better!

I think the neutral is perfectly fine here as we don't really treat this as an error. If we can't find your template we just swallow the octokit.content.get error and continue on creating your PR without a template body, and notify the user with that toast ^^

[ndom91]

@PavelLaptev pinging you for the UI / copy of this preferences section

What do you think? This is in the project preferences:

[estib-vega]

The code looks good to me 👍

[PavelLaptev]

@ndom91 thanks! lgtm

[koppor]

• Therefore, adding a settings path for folks to customize which PR template they want to be used.

i would have expected that Gitbutler auto detects the existance of the template. The paths are pre-determined by GitHub. I think, it are three (times two because of casing). See: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository

I agree, users can specify more in a directory github/PULL_REQUEST_TEMPLATE/. For that, the configuration is nice. I would have expected a drop down in this case.

Reason: GitButler is interacting with GitHub directly, not with arbitrary platforms. Thus, GitButler should make it convenient to interact with GitHub.

[ndom91]

@koppor thanks for the suggestion, I think if we check the few case-variants and then potentially list hte contents of a .github/PULL_REQUEST_TEMPLATE/ dir (if it exists), then we could easily offer this as a dropdown. I agree that'd be a ncier UX 👍