David Cramer
David Cramer
@jan-auer threw up initial thoughts on how we might approach this with an example
This is making me pivot back to my original concept of Changes (from Dropbox days), where my intention was to highlight an actual Changeset -- either one that originated via...
Additionally focusing endpoints at the root level (e.g. /builds vs /repos/XXX/builds) will make it easier to restructure the navigation to show all results vs repo-specific results (as a default).
(i had already started on some work on this, so will continue that)
Might be worth rethinking the complexity of source with this.. The way its designed is good to be able to just abstracting view any 'source' and all associated data, but...
Ok going Source -> ChangeRequest, as a PR/CR can have many sources over time and we'd want to track them uniformly.
Still working on this. Plan right now is: - You upsert a ChangeRequest - You upsert a source on a ChangeRequest (though we need to figure out how we approach...
Branch is ``feat/change-requests``
Decided on adding a 'head_revision' field (in addition to 'parent_revision') to ChangeRequest.
gonna rm -rf the Source relation for now as we dont need it and I dont want to add the complexity until it has a good reason for now you...