Skip to content

Semaphore overrides existing .semaphore config, on creating project #256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Joshhua5 opened this issue Apr 25, 2025 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@Joshhua5
Copy link

Describe the bug

The connecting a new instance of Semaphore to a project that I had already designed pipelines for, I found there was no choice to select the existing config, and after creating the project, the git history had the original file modified and overridden. Not a major issue thanks to Git history, worth reporting however.

Steps to reproduce

Create a project using a repository which previously had a Semaphore configuration.

Additional context

No response

@Joshhua5 Joshhua5 added the bug Something isn't working label Apr 25, 2025
@AleksandarCole AleksandarCole self-assigned this May 9, 2025
@AleksandarCole AleksandarCole moved this to Backlog in Roadmap May 9, 2025
@AleksandarCole AleksandarCole added this to the v.1.4 - Release milestone Jun 9, 2025
@skipi skipi moved this from Backlog to Todo in Roadmap Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

3 participants