You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume I should switch to using year ranges to align with the workflow and back-date the first year to the year the project started (which can be easily checked with GitHub)?
The update copyright GHA workflow we use (https://github.com/epiverse-trace/packagetemplate/blob/main/.github/workflows/update-copyright-year.yml) uses the range of years rather than updating a single year. I've been using a single year in Epiverse packages and updating them manually until now.
I assume I should switch to using year ranges to align with the workflow and back-date the first year to the year the project started (which can be easily checked with GitHub)?
All this bearing in mind that the years have little importance: https://daniel.haxx.se/blog/2023/01/08/copyright-without-years/.
The text was updated successfully, but these errors were encountered: