Skip to content

V2 format of codecoverage repository #1

@stazz

Description

@stazz

Currently the structure is fragmented so that single project has files in the following directories:

  • docs/<project-name>
  • history/<project-name>
  • badges/<project-name>

This stems from the fact that GitHub pages are nice to configure to read from docs folder of the master branch tip. However, the fragmentation is obviously not nice when working with the repo and generating and uploading code coverages. Furthermore, the partial clone is not as smooth with this structure.

The next version should instead make a symlink docs/<project-name> -> <project-name>/docs, and all of the project's data is stored in one top-level folder named as the project:

  • <project-name>/docs (where the symlink from docs/<project-name> to)
  • <project-name>/history
  • <project-name>/badges

The only question mark with this setup is how well GitHub page handles symlinks, which needs to be tested.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions