The `render` stage of site building may cause Git `fatal` errors for every rendered page

[johlym]

Bridgetown Version: bridgetown 1.0.0.beta2 "Pearl"

To Reproduce

• Have an existing Bridgetown site in a GitHub repository
• Pull the source tarball down from the repository for deployable branch (ex: wget -O - https://github.com/username/repo-name/tarball/master | tar xz
• cd into the resulting directory
• ensure the correct Ruby and Node.js versions are active within the environment
• run bundle install and yarn install to ensure all libraries are installed within the environment
• run bridgetown start or bridgetown deploy (any command that generates stuff for /output)

Current behavior Bridgetown builds the site as instructed

Expected behavior Bridgetown builds the site as instructed One copy of fatal: not a git repository (or any of the parent directories): .git is printed for every generated page in output (For Heroku, a second line is printed: Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).)

Screenshots

Computing environment (please complete the following information):

• OS: verified macOS 12.2 and Linux (Heroku)
• Browser: n/a
• Browser Version: n/a
• Ruby Version (check with ruby -v): Reproduced with Ruby 3.0.3

Additional context I do not see a reason why the render stage should need to do anything git-related. A proper .gitignore would omit any produced output, and if the site is being deployed elsewhere and not pulled down from source control using git clone, this will always be an issue–the render stage assumes it's always being run in within an active Git repo.

I confirmed this is happening in the render stage by way of adding puts statements in processable.rb. I lost the scent after that without shoving more puts in a bunch of places.

[jaredcwhite]

I'm not able to reproduce this (for example I downloaded https://github.com/bridgetownrb/fundraising-site/tarball/main, extracted it, ran bundle/yarn install, and ran bin/bridgetown deploy without issue). If you can produce a link to your repo with this issue, I'll investigate further.

[johlym]

Wild. Here's where I'm seeing it: johlym/johnathan-org. I'll keep poking at it–yank stuff out until it goes away.

[johlym]

I've narrowed this down to the bridgetown-sitemap plugin. ~I'll open an issue there.~ Opened https://github.com/ayushn21/bridgetown-sitemap/issues/1.