Overview

Right now we output a spurious message about reachability not being enabled for an org if it isn't. This PR removes it.

Acceptance criteria

Before:

After:

Testing plan

I manually tested by disabling reachability in my org, then runninig cabal run fossa -- analyze <project> and also fossa analyze <project>.

Risks

None

Metrics

Is this change something that can or should be tracked? If so, can we do it today? And how? If its easy, do it

References

conversation

Checklist

• I added tests for this PR's change (or explained in the PR description why tests don't make sense).
• If this PR introduced a user-visible change, I added documentation into docs/.
• If this PR added docs, I added links as appropriate to the user manual's ToC in docs/README.ms and gave consideration to how discoverable or not my documentation is.
• If this change is externally visible, I updated Changelog.md. If this PR did not mark a release, I added my changes into an ## Unreleased section at the top.
• If I made changes to .fossa.yml or fossa-deps.{json.yml}, I updated docs/references/files/*.schema.json AND I have updated example files used by fossa init command. You may also need to update these if you have added/removed new dependency type (e.g. pip) or analysis target type (e.g. poetry).
• If I made changes to a subcommand's options, I updated docs/references/subcommands/<subcommand>.md.