I would like to work on a set of features in branch features and merge with master once a set of features is added. This will trigger a chnage in production.
I would then continue to work on the features, in the branch features (I do not want, if possible, to open a new branche for each feature of the planned features set).
Is there a specific risk to do so, from git's perspective ?
I know that there are "best practices" for branch reuse but this development would be better orchestrated through a set of work on branch features -> merge with master -> continue working on branch features -> merge with master -> ...
I am the only developer, so master does not change between the merges.