Screenshots

Description

Preliminary support for custom markdown stylesheets. If there exists a “md-styles.css” file in the same directory as the markdown file being previewed this file is used as the stylesheet.

Font size for previews and editing are independent.

Changes tab uses the same font-size as when editing.

Fixed some bugs parsing .editorconfig files. It should work much better now.

Fixed auto-indentation in the editor.

x-callback-url/status no longer fails when there are deleted files.

x-callback-url/read can be invoked with type=url to return a universal url, which is useful when picking files in the start of a workflow.

Other minor fixes and adjustments.

v3.6.5
---------
Finally you can use Git Large File Storage (LFS) for your repositories with large binary files such as videos, images or audio. You don't need to do anything and can clone repositories as you normally do. Working Copy will download all needed assets when you checkout commits and upload changes to LFS objects as you push.
Any LFS enabled repositories cloned before this update will have LFS pointers in your working directory instead of real objects. The easiest fix is to clone the repository again.

When using Git Large File Storage you shouldn't notice, but the implementation was rewritten from scratch to work on iOS, as the regular Git LFS implementation requires command-line Git and a shell. This kind of effort was possible because enough people are purchasing the Pro unlock to support full-time development. Thank you for this.

The editor tries hard to adapt to your repository settings. It looks for encoding and indentation style in files with Emacs headers such as
-*- tab-width: 4; charset: utf-8; -*-
and it has been doing frequency analysis to make qualified guesses when there was nothing in the file header.

Now it also looks at .editorconfig files and uses these when the file header itself doesn't convey anything but before trying frequency analysis. GitHub and many other development tools support .editorconfig files and you should consider adopting them.

Improved behaviour of indent and unindent on iPad, especially for files mixing tabs and spaces.

When looking at merge commits you are shown changes compared to the mainline parent instead of both parent commits.

Inside the Files app the .git directory can no longer be entered like regular directories as there was nothing regular about it.

What’s New

Version 3.6.8

Preliminary support for custom markdown stylesheets. If there exists a “md-styles.css” file in the same directory as the markdown file being previewed this file is used as the stylesheet.

Font size for previews and editing are independent.

Changes tab uses the same font-size as when editing.

Fixed some bugs parsing .editorconfig files. It should work much better now.

Fixed auto-indentation in the editor.

x-callback-url/status no longer fails when there are deleted files.

x-callback-url/read can be invoked with type=url to return a universal url, which is useful when picking files in the start of a workflow.

Other minor fixes and adjustments.

v3.6.5
---------
Finally you can use Git Large File Storage (LFS) for your repositories with large binary files such as videos, images or audio. You don't need to do anything and can clone repositories as you normally do. Working Copy will download all needed assets when you checkout commits and upload changes to LFS objects as you push.
Any LFS enabled repositories cloned before this update will have LFS pointers in your working directory instead of real objects. The easiest fix is to clone the repository again.

When using Git Large File Storage you shouldn't notice, but the implementation was rewritten from scratch to work on iOS, as the regular Git LFS implementation requires command-line Git and a shell. This kind of effort was possible because enough people are purchasing the Pro unlock to support full-time development. Thank you for this.

The editor tries hard to adapt to your repository settings. It looks for encoding and indentation style in files with Emacs headers such as
-*- tab-width: 4; charset: utf-8; -*-
and it has been doing frequency analysis to make qualified guesses when there was nothing in the file header.

Now it also looks at .editorconfig files and uses these when the file header itself doesn't convey anything but before trying frequency analysis. GitHub and many other development tools support .editorconfig files and you should consider adopting them.

Improved behaviour of indent and unindent on iPad, especially for files mixing tabs and spaces.

When looking at merge commits you are shown changes compared to the mainline parent instead of both parent commits.

Inside the Files app the .git directory can no longer be entered like regular directories as there was nothing regular about it.

Ratings and Reviews

4.9 out of 5
579 Ratings
579 Ratings
Sean D. Hunt ,

good but why have push pro only?

I find it stupid that pushing is a pro only feature. Because of that this app becomes useless after the trial forcing me back to the even more useless git2go because I cant zip up a repository that I cloned on my phone and transferred to my laptop to make changes and commited on to push it on my phone as the laptop has no internet as the wifi driver in 1803 and the latest windows insiders keeps disconnecting me. This is why I got this app to replace that trash app but with push being pro it makes this one trash too. Sorry but if you want people want to be able to use it without them being forced to buy pro or people like me who cannot get a job because of my mental stability and so I do open source to pass time. Please take this into consideration. I love the fact of gpg signing too something git2go does not have. Although I would like it if I could press some rebase button on a commit that asks me if I want to squash it into the previous commit and possibly ones after it or fixup the previous one using only the currently opened one to basically amend the one before it. Other than that keep up the good work. :wink: Even I would like to help with making this app if it itself was also open source.

Developer Response ,

I need to make push a pro feature to make the people seriously using the app pay for it. It can support the salary of one developer (me) and I work full time to improve it.

This is frustrating when it's too expensive, but the alternative would not be better for you.

I wouldn't have been able to spend much time developing a free app as it would be done after completing my paying day job and the result would not be close to the quality that Working Copy is now.

I'm working on ways to amend, squash and split commits.

Seattle Rex ,

What Can I Do For Everyone Else Always?

I'm just a little burned out on the App Store shenanigans lately. I've lost count of the number of "Pro" upgrades of purchased which are now "free" and covered with ads. I'm tired of plunking down cash for expensive programs that, months later, switch to a subscription model, taking my cash and flushing it in the process. I'm tired of paying for apps, only to find them still filled with Ads. Maybe I'm just having a bad run, but the App Store truly feels like a scammer's bazaar these days. There are pick-pockets everywhere. I don't really lump the Working Copy folks into the group ... because they at least make a quality product and seem to put real effort into it. This is why I paid for a "permanent" Pro upgrade 14 months ago. And just paid $8 again for another "permanent" Pro upgrade. Like many other things, "permanent" doesn't mean what I thought it did. I'm sure it it's worth it, and I'm glad to support them, I just feel a little burned out and a little "over-used". I bought last Christmas and it just doesn't feel that long ago to get hit up again. I feel like I get rolled like a drunken sailor every time I log into the app store these days. I really like the app though. Nice work, guys.

Developer Response ,

Hi Rex, I understand that it can feel a bit much with many apps asking you to pay again and again. The upgrade mechanism in Working Copy is made to be fully voluntary. You can delay upgrading if the added pro features are not enticing and you can decide never to upgrade and the pro features you already have will stick around forever. The app will still be updated with bug-fixes and non-pro features without you having to pay again. If you can accept a delay in when you get the latest pro features every other year you could even delay purchasing the upgrade, such that you only upgrade every 24 months keeping down the costs.

neural_bites ,

Second rating

Hello.

I am back. I like the way you can import projects from virtually anywhere and edit on your phone. But there’s bugs. I hate bugs. Do you like bugs? Ok. So. When your in the middle of editing something and copying from here and pasting into there. And then you go back one too many pages. And it hits you, when you can’t find the netbeans project folder. Because working copy deleted it. It hits you. That you just got fooled. Working copy isn’t what you thought it was going to be. No, not the application that seamlessly edits and commits with NO bugs. Not that one. Maybe in the next lifetime. Some app will do what it “claims to do” and everyone will be happy.

If you read this till the end, good job.

Developer Response ,

I don't like bugs either and I want them gone from the app. If you have any details about what happened please email me at anders@workingcopyapp.com and I will work to improve this.

Information

Seller
Anders Borum
Size
69.8 MB
Category
Productivity
Compatibility
Requires iOS 11.4 or later. Compatible with iPhone, iPad, and iPod touch.
Languages
English
Age Rating
Rated 4+
Copyright
© Anders Borum 2014
Price
Free
In-App Purchases
  1. Pro Unlock $15.99
  2. Pro Unlock trial Free
  3. Pro Upgrade $7.99

Supports

  • Family Sharing

    With Family Sharing set up, up to six family members can use this app.

More By This Developer

You May Also Like