Describe what you're going to do in issue before doing anything

As proposed by @Ostrzy. That way no one will be surprised by big pull-request, as everyone will be at least notified you're going to change something.

This is connected to my refactor in ghcr, but I see other people doing that as well, for example @teamon in rails-assets, which is indeed annoying.

This guideline is mainly for open source and internal projects.

Such issue can be easily converted to pull-request later on.