Update pull_request_template.md

[OfryL]

ℹ️ PR description:

updating pr template to our new flow

📋 PR tasks:

• Meaningful description
• Risk Assessment¹ - 🟢Low
• Jira - https://autofleet.atlassian.net/browse/AUT-17065
• Manual QA
• E2E test
• Code review

Footnotes

1. Deploy By Risk Level – FigJam ↩

[atlowChemi]

@OfryL @dorshay6 I think using Github labels would be easier:
It would allow selecting one without the need of editing the description, it would be more visible (no need to enter PR in order to see it) and we could search PRs based on it much easier...

[OfryL]

@OfryL @dorshay6 I think using Github labels would be easier: It would allow selecting one without the need of editing the description, it would be more visible (no need to enter PR in order to see it) and we could search PRs based on it much easier...

Relevant labels were added in org level, this will effect new repos only.

[atlowChemi]

Relevant labels were added in org level, this will effect new repos only.

@OfryL I think we should prefer labels due to their advantages, and add them as we go... (anyone opening a PR in a repo which doesn't have the labels yet should add them to that repo)

[ofek-autofleet]

@atlowChemi how would these labels work?
@OfryL i think the risk assesment should stay in the jira, to be our source of truth (these might change and we don't want to change it in 2 places)
i also think the meaningful descriptions should be elaborate
also add a unit test square and todo section (maybe stuff left until finished)

[atlowChemi]

@atlowChemi how would these labels work?

Not sure what you mean by "work".
An individual opening a PR would mark the PR with the relevant label based on his assumption.
This would allow the reviewers to be more alert when reviewing yellow/red PRs, and it would allow having a documented discussion if someone disagrees with the risk assessment...

@OfryL i think the risk assesment should stay in the jira, to be our source of truth (these might change and we don't want to change it in 2 places)

We could add a GHA that updates Jira by API when a PR label is changed...