Been a little quiet I know, but it's also been a little busy for me. Which is all good, but it meant I had to stop work on Codaset for a short while. Well all that is now at an end, and I am pushing with all my weight on getting Codaset out of beta, and giving you guys the features you want and need. So without further ado, I give you the latest and greatest Codaset release yet!
As previously mentioned, this releases main new feature is a fully functional Push API, which allow you to create notifications or pushes. These pushes can then post to a webhook, or tweet to your Twitter account, when a specific event occurs. Right now, webhooks and twitter pushes are supported, and others are planned. But let me know what other kind of push services you would like us to support.
You can create a push for up to 24 individual user and/or project events. So unlike the previous Twitter notifications that Codaset supported, you now have full control over what exactly you tweet about. So if you only want to send a tweet when a new ticket is created within your project, just select the "Create Ticket" event when creating your push.
As well as giving you the ability to automatically tweet about your project's activity, you can also create a webhook push. If you are unfamiliar with webhooks, you should check out http://webhooks.pbworks.com/, which should help you understand and really appreciate what webhooks can do for you.
In a nutshell, a webhook is a simple HTTP post to a given URL. So if you create a new webhook push for when a Git commit occurs on your project, Codaset will call the URL you provide, and post a payload to it. That payload will be a JSON object with data about the event in question. Take a look at our test Postbin for a little more on how the webhooks would look.
So the Push API is just the first step in opening up the Codaset system to you. The second, and somewhat larger step, is the all inclusive API that will be available by the time we come out of beta. But for now, you have a great way to plug into your project and user activity on Codaset. I would love to hear any thoughts and feedback on the API, and would also love to know what you guys might do with it. Please let me know.
Over the last month or two, I have had several comments on the navigation system, and how crowded it looks. And as more and more features are added, that would only get more crowded, and less user friendly. So earlier this week I set about improving that experience of navigating your projects. What resulted is a much leaner, cleaner and more user friendly navigation, which has been rolled out across the site as of today.
Not much more to say about that really, but I think it looks and feels much better, and I hope you do too.
I also added a copy to clipboard link next to the Git clone URL's, which will make it much easier and faster to clone your Git repositories.
A number of small bugs have also been fixed...
I hope you enjoy this weeks release. Please check out the current list of tickets to see what else is in store. If there are any that you would really like to see sooner rather than later, please vote them up. And if there is something you would like to see, but there is no ticket created, please feel free to create one.
Thanks again. Enjoy!
That's great work Joel.
Anyway, In the recent updates of Codaset I received this warning from git:
warning: updating the current branch
warning: Updating the currently checked out branch may cause confusion,
warning: as the index and work tree do not reflect changes that are in HEAD.
warning: As a result, you may see the changes you just pushed into it
warning: reverted when you run 'git diff' over there, and you may want
warning: to run 'git reset --hard' before starting to work to recover.
warning:
warning: You can set 'receive.denyCurrentBranch' configuration variable to
warning: 'refuse' in the remote repository to forbid pushing into its
warning: current branch.
warning: To allow pushing into the current branch, you can set it to 'ignore';
warning: but this is not recommended unless you arranged to update its work
warning: tree to match what you pushed in some other way.
warning:
warning: To squelch this message, you can set it to 'warn'.
warning:
warning: Note that the default will change in a future version of git
warning: to refuse updating the current branch unless you have the
warning: configuration variable set to either 'ignore' or 'warn'.