Docs: Fixes on COVERALLS_FLAG_NAME and COVERALLS_REPO_TOKEN for GitHub Actions #244
…b Actions Details: * The docs section 'Github Actions Gotcha' stated that the COVERALLS_FLAG_NAME env var is needed in order to avoid 'pile up of jobs'. It turns out that it is optional, and when specified, can be specified with the same value across all jobs or with unique values. This change clarifies that in the documentation. * This change also clarifies that the COVERALLS_REPO_TOKEN env var is not needed for GitHub Actions. * This change also renames the heading of the section to 'Github Actions support' to have a more neutral name. Signed-off-by: Andreas Maier <email@example.com>
TheKevJames left a comment
@andy-maier thanks for the contribution, and I appreciate you helping to clean things up here. As you mentioned in #243, I think it would be useful to mention something about the "piling up" of jobs, even if it's not something we can fix. Could you include something to that effect here, to make sure users know that is expected?