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
{{ message }}
Repository navigation
add-doi: confirm the Zenodo website link, accept the community request, and output the data availability text (after washr 1.3.0) #99
Community request. guluswm's .zenodo.json listed the openwashdata community, yet the record appeared without it until it was added by hand in the Zenodo editor. The GitHub integration submits a community request that a curator has to accept. Step 7 should say so and point to the community's request inbox, so the record does not stay outside the community.
Two deviations from the issue text in the coming PR:
The data availability text is not the last step of add-doi. It is the new Step 9, before the dev sync and the development version (now Step 10). Run after Step 10, washr::data_availability_statement() would read the x.y.z.9000 version from DESCRIPTION and name an unreleased version. The step runs on main and first asks for the opening words of the statement, with "The data" as the default.
The floor bump to 1.3.0 also covers the /washr skill preflight, which needs only 1.2.1 by itself, so that all skills share one floor as in 1.8.0.
Activity
larnsce commentedon Nov 3, 2026
Two deviations from the issue text in the coming PR:
add-doi. It is the new Step 9, before the dev sync and the development version (now Step 10). Run after Step 10,washr::data_availability_statement()would read thex.y.z.9000version from DESCRIPTION and name an unreleased version. The step runs onmainand first asks for the opening words of the statement, with "The data" as the default./washrskill preflight, which needs only 1.2.1 by itself, so that all skills share one floor as in 1.8.0.