Triggering tests in stardis after every push to master branch

[KasukabeDefenceForce]

📝 Description

Type: 🪲 bugfix | 🚀 feature | ☣️ breaking change | 🚦 testing | 📝 documentation | 🎢 infrastructure

Triggering tests workflow in stardis after every push to the tardis master branch. This is related to #201 in stardis.

📌 Resources

Examples, notebooks, and links to useful references.

🚦 Testing

How did you test these changes?

• Testing pipeline
• Other method (describe)
• My changes can't be tested (explain why)

☑️ Checklist

• I requested two reviewers for this pull request
• I updated the documentation according to my changes
• I built the documentation by applying the build_docs label

Note: If you are not allowed to perform any of these actions, ping (@) a contributor.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.57%. Comparing base (c107f27) to head (c11edf4).
Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2708      +/-   ##
==========================================
+ Coverage   36.47%   36.57%   +0.10%     
==========================================
  Files         183      184       +1     
  Lines       14664    14765     +101     
==========================================
+ Hits         5348     5401      +53     
- Misses       9316     9364      +48     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.