Following the same pattern as inject and some hooks, useful for when getting debug logs.
One worry I have, same as when used elsewhere, is that version.c doesn't get rebuilt every build, allowing it to become stale. Does the Makefile system allow specifying a force-rebuild target?
Following the same pattern as `inject` and some hooks, useful for when getting debug logs.
One worry I have, same as when used elsewhere, is that version.c doesn't get rebuilt every build, allowing it to become stale. Does the Makefile system allow specifying a force-rebuild target?
One worry I have, same as when used elsewhere, is that version.c doesn't get rebuilt every build, allowing it to become stale. Does the Makefile system allow specifying a force-rebuild target?
Not that I am aware of. The current way to do this is running clean builds whenever something gets actually distributed. So taking builds from our CI pipelines are fine, for local dev builds, you have to manually run a clean build. Not great, but the important stuff (official bin releases) works for now.
> One worry I have, same as when used elsewhere, is that version.c doesn't get rebuilt every build, allowing it to become stale. Does the Makefile system allow specifying a force-rebuild target?
Not that I am aware of. The current way to do this is running clean builds whenever something gets actually distributed. So taking builds from our CI pipelines are fine, for local dev builds, you have to manually run a clean build. Not great, but the important stuff (official bin releases) works for now.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Following the same pattern as
injectand some hooks, useful for when getting debug logs.One worry I have, same as when used elsewhere, is that version.c doesn't get rebuilt every build, allowing it to become stale. Does the Makefile system allow specifying a force-rebuild target?
Not that I am aware of. The current way to do this is running clean builds whenever something gets actually distributed. So taking builds from our CI pipelines are fine, for local dev builds, you have to manually run a clean build. Not great, but the important stuff (official bin releases) works for now.
In that case, I just added that functionality. :)