Make update-refdata pipeline open a PR instead of merging changes

[epassaro]

Description

Change in the update reference data. Now opens a PR in the tardis-refdata repository instead of pushing the changes.

Example: https://github.com/tardis-sn/tardis-refdata/pull/54/files

Motivation and context

For security purposes.

How has this been tested?

• Testing pipeline.
• Other.
• [ ]
  By the pipeline itself.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[codecov]

Codecov Report

Merging #1900 (f9f039f) into master (69b433c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1900   +/-   ##
=======================================
  Coverage   61.17%   61.17%           
=======================================
  Files          69       69           
  Lines        7331     7331           
=======================================
  Hits         4485     4485           
  Misses       2846     2846           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 69b433c...f9f039f. Read the comment docs.

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[epassaro]

/azp run update-refdata

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).