Turn off CI for forks

[Eric-Arellano]

Summary

Most people agree that GitHub made a mistake by having forks run CI both on the fork and in the upstream repository. It wastes computing resources (which has a real environmental cost!). In this repo in particular, the nightly integration tests have been failing for me.

Details and comments

If people really want to run CI in their fork, they can always modify their fork's config to revert this change.

[qiskit-bot]

Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the the following people are requested to review this:

• @Qiskit/terra-core

[coveralls]

Pull Request Test Coverage Report for Build 4885330331

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 29 unchanged lines in 6 files lost coverage.
• Overall coverage increased (+0.03%) to 85.897%

---

Files with Coverage Reduction	New Missed Lines	%
qiskit/transpiler/passes/synthesis/unitary_synthesis.py	1	90.46%
crates/qasm2/src/lex.rs	2	90.89%
qiskit/extensions/quantum_initializer/squ.py	2	80.0%
crates/accelerate/src/sabre_swap/layer.rs	4	97.32%
crates/accelerate/src/vf2_layout.rs	8	86.44%
crates/qasm2/src/parse.rs	12	97.11%

Totals
Change from base Build 4876894924:	0.03%
Covered Lines:	71239
Relevant Lines:	82935

---

💛 - Coveralls

[kdk]

LGTM. I haven't seen any reason to run these tests on forks.