Undid restrictions for on: push triggers

[oleksandr-pavlyk]

This undoes questionable change from #634, specifically this one:

index 4e70c39c..6b99baf3 100644
--- a/.github/workflows/conda-package.yml
+++ b/.github/workflows/conda-package.yml
@@ -1,6 +1,9 @@
 name: Conda package
 
-on: push
+on:
+  push:
+    branches:
+    tags:
 
 env:
   PACKAGE_NAME: dpctl

The net effect of this change was that workflow was disabled, since branches and tags requirements were never met.

[coveralls]

Coverage remained the same at 74.511% when pulling 8cea9a0 on undo-workflow-damage into 9bc9b43 on master.

[PokhodenkoSA]

@oleksandr-pavlyk
Could you please provide example of PR where this workflow should start but did not start?

[oleksandr-pavlyk]

#636 was the one. Because it was opened from a fork, the push trigger was not met and windows build and test workflow did not run.

[PokhodenkoSA]

It run in author's branch.

https://github.com/diptorupd/dpctl/tree/fix/dll_load

It is because author pushed to his repository. So it will use his secret tokens and will not upload anything to our anaconda channels.

[PokhodenkoSA]

This is a security issue I would like to know how to solve with pull_requests trigger.
I am afraid it will run with our secret tokens.
There is some protections from GitHub like asking for approve before CI run. But I did not investigate it yet with good level of confidence.