All new code requires tests to ensure against regressions.
However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.
[X] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
This PR adds our first badge to the backend. A simple 'Made for Pulsar!' success badge.
This badge is determined by delivery time, and requires zero change within the actual data of the package.
Simply when delivering a package to the end user, the backend will check the creation method of the package, and if it contains the string "User Made Package" (Which is only applied to packages made through the backend) then we give it this badge.
It's a simple way of letting users know that a package is more likely to work than not. And helps highlight some of the package creators we have on the Pulsar ecosystem.
Requirements
Filling out the template is required.
All new code requires tests to ensure against regressions.
[X] Have you ran tests against this code?
[ ] This PR contains zero code changes.
Description of the Change
This PR adds our first badge to the backend. A simple 'Made for Pulsar!' success badge.
This badge is determined by delivery time, and requires zero change within the actual data of the package.
Simply when delivering a package to the end user, the backend will check the creation method of the package, and if it contains the string "User Made Package" (Which is only applied to packages made through the backend) then we give it this badge.
It's a simple way of letting users know that a package is more likely to work than not. And helps highlight some of the package creators we have on the Pulsar ecosystem.