Update PULL_REQUEST_TEMPLATE.md

[aboydnw]

The PR template seems a little outdated, so updating with some checklists of frequent items that come up during reviews.

[netlify]

✅ Deploy Preview for visex ready!

Name	Link
🔨 Latest commit	2342140
🔍 Latest deploy log	https://app.netlify.com/sites/visex/deploys/6731b3b0c970230008ffaa83
😎 Deploy Preview	https://deploy-preview-486--visex.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dzole0311]

Should we add a third one for when we only pull-in the latest veda-ui updates?

[aboydnw]

@dzole0311 I like that idea! I'm not very familiar with that process though. Would you or @sandrahoang686 @hanbyul-here be able to suggest a checklist?

[hanbyul-here]

oki I took a stab and pushed the change. (I also edited the doc about updating veda-ui) Let me know how it looks!

[hanbyul-here]

I have a question - did you list out the possible options on purpose? Currently, the PR asks you what kind of change you are making and takes you to the right template - Your approach can save a click so I don't really mind the change, but I just wanted to confirm if this was intentional (If so, we need to delete the files in the folder https://github.com/US-GHG-Center/veda-config-ghg/tree/develop/.github/PULL_REQUEST_TEMPLATE )

[aboydnw]

@hanbyul-here the PR template you linked to is in veda-config-ghg. I don't think we have the same template(s) for veda-config. Maybe it's just about pulling over those PR templates? If they work better, I'm open to doing that too.

[aboydnw]

I'll go ahead and merge this PR and we can update the template again based on what we want to do with the veda-config-ghg template

[hanbyul-here]

@aboydnw Urg sorry, I meant these files : https://github.com/NASA-IMPACT/veda-config/tree/develop/.github/PULL_REQUEST_TEMPLATE
I really do not have a good idea if just removing the unrelated parts is more convenient for users or clicking to the specific one is better. But we just need to be coherent (if we are making a user to delete unrealted parts, remove the files in PULL_REQUEST_TEMPLATE, if we want a user to follow the previous workflow, split the current contents into each template and retrieve the previous links)