I've added CircleCI to my project, as instructed in the guide. It's working well, except my GitHub releases page is cluttered with multiple tags for every commit. Moreover, external contributors watching our repo are being inundated with notifications about new releases being pushed; when in fact, we're just iterating of diffs.
In the Harbormaster User Guide, you call out this problem, and suggest using a separate repo for the staging area. Why is the Staging Area based on tags? Naively, it seems like branches would be better suited to this: they're easier to browse, not conflated with releases, and often used to stage in-progress work.
If branches are a sufficient alternative for Staging Areas, those would be preferred (to avoid Release clutter). If not, documentation of the problem in the Harbormaster Guide would dissuade people like me from opening issues like this. More importantly, if we know the limitations, we can help craft a solution.