Josh Smith

Update project factory so a set of task lists is always created

6

# Problem We should upgrade our project factory so a set of task lists is always created. In a real use scenario, projects cannot get created without associated task lists....

Refactor mix environment files so they are untethered from deployment configurations

3

# Problem Per some advice from @DavidAntaramian: > In essence, your Mix environment is not the same as a Rails environment. Very different beasts. The Mix environment should only control...

Alias user on create

1

# What's in this PR? Allows us to alias the user on creation. This is a WIP and very much incomplete. A few of the issues we have with this:...

# What's in this PR? Optimization tweaks for the rendering of task lists. Needs tests.

Syncing does not match ResultAggregator errors

1

# What's in this PR? Right now this PR just has a failing test case demonstrating that syncing does not match `ResultAggregator` errors in the form of `{:error, {list, list}}`....

Ensure GitHubRepo is always find or create

2

# What's in this PR? WIP. ## References Progress on #1077

Epic: Implement GitHub integration sync

5

# Problem We need to reliably and concurrently sync tasks and comments to and from GitHub in a non-blocking way. By providing a timestamp-based concurrency control system we can use...

Reorganize GitHub modules

4

# Problem Much of the GitHub syncing can be reorganized as follows: - [x] `CommentSyncer` and `TaskSyncer` need to move out of `Event`; structure could be like: - `sync/issue/issue.ex` `Sync.Issue`...

Fix long description validation

1

# Problem EDIT: See the comment below. We want to have a place for a `Project` to be explicitly approved by an admin.

Fix validation errors for timestamps in GitHub syncing to not error but ignore

3

# Problem Right now if there are validation errors due to timestamps being off in GitHub syncing, it appears we're seeing `validating_tasks` or `validating_comments` errors. What we should do instead...