If an user changes an attribute of the configuration that does not send an event to the server and then it updates the config file their first action (if done via the web) will disappear.

To reproduce:

• Create the .dothub.repo.yml file
• Update the repository description
• Change anything in the .dothub.repo.yml file
• You will see that the change you made in step 2 will be erased

At the moment the owner is named organizarion. But for user repos it makes no sense. It should be named owner instead

Option to configure all repositories of an org. Should have an flag to override the repos that have a .dothub file

The tool should keep in sync manual changes to the repo/org configuration

The web app files to update the file with a 404 being returned when an event is received an it attempts to sync the file

At the moment dothub-web only works by inviting the user to the organization. This means that dothub cannot handle single repos nor repos within an user. We need to figure out how to workaround the issue.

The current file is just a dev file. Either document how to use it via flask or just create a file to run it properly.
At the moment is just running the dev server.

Document that:

• dothub-web only works when dothub-bot is added as owner to the org
• The webhook needs to be added as json and for all events
• Users need to add the file first

At the moment the dothub push --bulk mariocj89/* fails on users as it tries to hit http//api.github.com/orgs/mariocj89/repos instead of http//api.github.com/users/mariocj89/repos.

dothub should retrieve the repo list from the right url, detecting whether the owner is an org or an user.

The organization and repo needs to be passed every time the command is run and this can be inferred from the repo

Team configuration includes an attribute "id" which should not be exposed as creating a team will fail if the id is provided.

Whether we include ids or not it should be consolidated so it is consistent across the multiple objects with ids (example: labels don't expose ids in dothub)

At the moment configure is run whenever we run the app for the first time and it has some limitations like not being able to specify a custom github url to create the token.

Configure should be a command on its own and it should be possible to configure things like the github api as well for the token creation

Define a template to be applied to the new repos added to the organization so when you create a new repo a default configuration is applied

Basic up that just listens to github events

Consider using github integrations

The same way we can configure repos we should be able to configure organizations

When the diff is presented, if you say "n" it will still perform the changes

Create a GitHub user for the tool and use it to do end to end testing. Add the user token to travis as an env var so it can run the tests.

Allow users to set a webhook such that when they update their config files it updates automatically their repo configuration

def main():
    logging.basicConfig(levle=logging.INFO, format="%(message)s")
    conf = config.load_config()
    cli.dothub(obj={}, default_map=conf)

levle -> level

Could you also update PyPI as it's currently broken.

At the moment hooks are indexed by their name, but all web hooks have the name "web" which make them collide.

There are multiple ways to fix it:

• Have two sections "webhooks" and "services" where services are all hooks with the proper name. Following GitHub naming
• Make the hooks configurable as an array having the name as a property of each section

Same applies to organization

Create a plugin for Travis to allow users to keep their repositories up to date.

It needs to be check if the repo file changed, and if so, update the config file.

We need to find a way on how to keep the file up to date in case the settings are changed via the web.

Quite often repositories have configuration as files. .travis files as an example. This issue is to explore using dothub to create/update those

Steps to reproduce:

• Pull the config of a repo
• Remove a section (so you don't want to get it synced, eg hooks)
• perform a pull again
• hooks are added (ideally they should not be)

Allow users to skip a field being retrieved from github. So if user don't want to display the description of repositories they can just list it as ignored.

A possible implementation is just to ignore the fields that are removed from the local config file.

At the moment, removing the description from dothub file gives the following output:

Pushing '.dothub.repo.yml' to 'dothub-sandbox/test-repo'
Changes:
- root['options']['description']
Apply changes? [Y/n]:

Even though the description is not updated

At the moment renaming a label losses all the issues that were assigned to it, as it effectively deletes the existing and creates a new one.

It answers an 400 otherwise

Users can change the config file at will, we need a way to validate it

The same way we pull/push an org configuration we should be able to do it for users.

Commands will be:

dothub pull <username>
dothub push <username

We can "shoe it" into an org but it is far from clean an ideal. A new object should be created in the same way orgs and repos are.

Warning: This is not a simple not quick issue, please reach out before starting if you pick this up.

Once click 7.0 is cut. Use the hidden feature to hide org/repo and emit a deprecation warning. After a considerable time, just drop them.

These are the already marked as deprecated dothub org and dothub repo option groups

Some users complain about the cli not being intuitive, study and consider adding a more intuitive approach like:

Repositories:

Retrieve configuration:
dothub pull org_name/repo_name

Update configuration:
dothub push org_name/repo_name

Organization:

Retrieve configuration:
dothub pull org_name

Update configuration:
dothub push org_name

Update multiple repositories:
dothub push org_name/*

The * can be a gob pattern/regex to match multiple repositories

Improving tests:

Additionally, use this change to stop "guessing" the git repo if provided as it can cause issues for some users even at tests time

Before updating repo/organisation ask for user confirmation display the changes

Hi, thanks for this tool.

Is there a way to apply all changes without validation ? That way the tool could be run as a cron or a travis job easily.

A website that just gives the bot access to the org/repo so users can enable dothub clicking a link

Add a section for branch support.

Features that can be included are:

• Adding/editing branch commit (this might be a pain as the commit can be updated to frequent)
• Branch protection

To be refined before actual implementation

At the moment if no options or no hooks are specified it will remove all of them, we should change it so if a whole part of the config is not provided to be skipped. This is really useful for org.repos command as it allows to define organzation level configuration for a subset of the config onle

At the moment for dothub to work we need to connect to the dothub-bot account and accept the invitation to join organizations. That needs to be fixed!

At the moment because webhooks can have the key value token config with secret tokens we dont support them, we need a better approach

If a section is not present it will appear as missing in the confirmation when updating the GitHub config. As optional means ignore now it should not appear in the diff

At the moment writing new labels is not intuitive as it requires to write the colors using their hex code. See:

labels:
  bug:
    color: 000000
  enhancement:
    color: ff0000

Whilst some gifted minds are able to map those to common word colors normal humans prefer words like "red", "blue", etc.

This issue is to add support so the most common colors can be also specified as words. For ease of implementation, those will be also retrieved as a word at retrieve time. An option to dothub should be added in the future to deactivate this functionality.

The objective is to be able to configure the labels as:

labels:
  bug:
    color: black
  enhancement:
    color: red