Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Activity for HeavyRain
| Type | On... | Excerpt | Status | Date |
|---|---|---|---|---|
| Comment | Post #295336 |
I disagree on your take that refactoring always means "I didn't consider requirements and/or design enough". Sometimes you just don't know enough and need a balance between analysis paralysis and quickly getting a feature out. Requirements change. New technologies become available. Code cleanup s... (more) |
— | 6 months ago |
| Comment | Post #293029 |
That is a crazy cool idea. Totally avoids the `ignoreRevsFile` file. Relies on convention of commit messages. I wonder if this would have performance impacts. Maybe I need a cron job to regenerate my `ignoreRevsFile`, or do that at each `git pull` and don't check it in. I need to think about this. (more) |
— | almost 2 years ago |
| Edit | Post #293029 | Initial revision | — | almost 2 years ago |
| Question | — |
How to keep git blame ignored commits up to date? When I make a separate commit for code cleanup / style changes, I can suppress that commit from `git blame` so that I can follow a file's history easily without getting distracted by pure style changes. I do that by putting the cleanup commit's hash in a file and tell git to ignore those commits ... (more) |
— | almost 2 years ago |