You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Git rebase a lot in my flow but noticed that direnv activates every time I rebase even though no relevant files have been changed, e.g. when the only new commit is a merge commit of current branch onto main. Is there any way to avoid re-activating direnv during rebase? I thought that something like .direnvignore would be useful, but couldn't find anything related in the docs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I use Git rebase a lot in my flow but noticed that direnv activates every time I rebase even though no relevant files have been changed, e.g. when the only new commit is a merge commit of current branch onto main. Is there any way to avoid re-activating direnv during rebase? I thought that something like
.direnvignorewould be useful, but couldn't find anything related in the docs.Beta Was this translation helpful? Give feedback.
All reactions