search

gbif / doc-effective-nodes-guidance

Repo for prototype documentation used to establish an integrated workflow to produce, maintain and publish GBIF documentation
https://doi.org/10.15468/doc-z79c-sa53
Other
2 stars 2 forks source link

Remove directory structure and long filenames. #20

Closed MattBlissett closed 5 years ago

MattBlissett commented 5 years ago

Build status

On the main README this is a link to the Jenkins build job, and clicking the red circle shows the error messages.

po4a.conf:14: The '3.-why-are-participant-nodes-needed/box-2.-stakeholders-involved-in-gbif-activities-at-the-participant-level.en.adoc' master file does not exist.

It's been renamed, along with lots of other files. The long directory and filenames are unwieldy, so (towards #17) I've renamed them, and deleted the ones that have had their content copied into the main section part. Also to test using a pull request.

(Another reasonable option would be filenames like 420-supporting-biodiversity.en.adoc.)

kcopas commented 5 years ago

Thank you, Matt—I had changed several file names but was going to save the purge for my next pass.

You’re right to remind me to use pull requests—still not a habit!

MattBlissett commented 5 years ago

It's your document, so there's no need for you to create pull requests — there's no point, since you're the one approving and merging them anyway.