unignore dist on main branch

[robertkowalski]

currently the ignore is not needed on the main branch and we are running into a bug with nektos/act which uses the go-git library.

go-git/go-git#633

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a44530

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Andarist]

Without ignoring this we will end up with constant merge conflicts. Each PR merged will create conflicts in all pending ones. I'd really like to avoid that - it's super frustrating, especially when it happens to the community PRs

Is there any open issue in nectos/act related to this?

[robertkowalski]

@Andarist not yet, we opened one in go-git as the error originates from there: go-git/go-git#633

[Andarist]

I would wait for that issue to be resolved first then. How do you end up with this problem in the first place though? I don't quite understand the full e2e scenario that you are facing. Is nektos/act fetching our main branch and then switching to the "requested" ref? I assume that you are using changesets/actions@v1 or something like that and not changesets/action@main