Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to prevent a file from being committed to one branch but included in the commit for another?

We have a cert file that belongs in our development area and we don't want to push it up to our production area.  We have separate branches for each area.  There is actually a cert file also for the production area.  So every time we commit from our development area to our production are the dev cert gets included in the production area and it causes issues.  Is there a way to have the dev cert belong to the dev branches (we have a dev, qa, and staging branch for each environment) and the prod cert belong only to the production branch ?

Any ideas or suggestions would be greatly appreciated!

1 answer

0 votes
Mike Corsaro Atlassian Team May 15, 2018

Hello! This should be possible using .gitattributes. I assume your workflow is to merge from dev to prod? If so, you can use something like this to achieve that.

We actually have three development environments that use the same sandbox SSL cert (required by a third-party API) and it is only one file that needs to remain on those servers.  A different SSL cert is used by the production version of the API.  THe cert shouldn't change very frequently.  We simply want to keep the cert files in the right location but don't want to commit them every time.  Right now we have to commit the prod cert separately to the repo after releasing code in order to keep the API working, because the sandbox version of the cert keeps getting committed with pushes to the dev branches.  Don't know how to fix this.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,291 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you