Probably by committing directly to master for every commit instead of merging from another branch when you're finished your new feature. I do this for small one person projects, i don't care if this commit breaks the build cause I'll fix it in the next one.
On 15 February 2018 at 19:54, mar77i via aur-general <[email protected]> wrote: > -------- Original Message -------- > On February 14, 2018 3:46 PM, Simon Doppler [email protected] wrote: > >>On Wednesday, 14 February 2018 15:29:29 CET Eli Schwartz via aur-general >>In this case, he should not publish the development code anyway, since nothing >> will stop users from submitting bug reports for development code (whether it >> is mail based bug reporting, mailing list based, using Git{hub,lab,*}-style >> issues or an actual bugtracker). >>Simon Doppler (dopsi) >> E: [email protected] >> > > > I seriously wonder, though. How *do* you so consistently break things between > releases? > > cheers! > mar77i > > > Sent with ProtonMail Secure Email.
