61–70 of 92 posts
Just to be clear, this appears as if it's some kind of web wrapper to `git add file.ext && git commit -m " " && git push`?
I think this is a great step, for several reasons -- both corporate and user-facing. (1) It is true that this is more likely to turn GitHub into a generic file-dump place similar to DropBox. GitHub's infrastructure is sufficiently good to handle this, and this new addition is unlikely to disrupt the workflow of veteran users. However, since it is likely that some companies will use GitHub for file dumping, GitHub wil…
Out of curiosity, I just tried uploading a file larger than 100MB to test the limits via the browser and received the following error:
Yowza, that’s a big file. Try again with a file smaller than 25MB.
[1] https://help.github.com/articles/conditions-for-large-files/
[2] https://help.github.com/articles/billing-plans-for-git-large...
I'm a bit confused, this is a simple git add or some sort of integration with git lfs they released last year? https://git-lfs.github.com
Earlier quoted context omitted.
I'd love to be able to search in branches. Especially on projects that commit to master and have release branches when they are between releases.
Well, as long as we're discussing search wish lists, I'd love case-sensitive search.
Search/code management metrics are done at the branch level and there will be case-sensitive searches. The indexers are already building case sensitive indexes, it's just that it hasn't been enabled.
Unfortunately I can't say when the indexer will be available for private use at the moment.
Edit:
Forgot to mention that because the indexing is done at the branch level, searching across branches to verify what is/isn't present is pretty trivial like the following example:
Earlier quoted context omitted.
Well as it's based on git, before you just had to push it via the command line.
No, there's always (read: for a long time) been a "New file" button that takes you here: https://github.com/user/repo/new/branch
I think this is a great step, for several reasons -- both corporate and user-facing. (1) It is true that this is more likely to turn GitHub into a generic file-dump place similar to DropBox. GitHub's infrastructure is sufficiently good to handle this, and this new addition is unlikely to disrupt the workflow of veteran users. However, since it is likely that some companies will use GitHub for file dumping, GitHub wil…
With a gist you're able to quickly and easily upload a single file script (or multiple files).
Also once created you can clone it as a git repo and make updates and push back to it (e.g. add files etc). Also people can fork your gist just like git repos.
I like this approach rather than creating a "new repository" on github for small scripts or snippets because then your github profile doesn't get cluttered with small snippets and script repos and is reserved for actual "project" repos.
Just to be clear, this appears as if it's some kind of web wrapper to `git add file.ext && git commit -m " " && git push`?
It makes github a more complete "gui" for git.
To be honest I don't feel that this is the right approach. But I'm a technical user so who knows. But it feels like github is forking off to a different direction.
Probably trying to look more "inviting" to corporate users; companies where sales are determined by non-technical managerial users. I can easily imagine such types asking questions like: "I want to upload a file to my team's repo, how can I do that?".
It would make it way easier for non-technical users to mess up the repo with tons of binary files, like images, movies, word documents, and excel sheets.
That seems to me like it would be much more valuable, specially for community projects.
I think this is a great step, for several reasons -- both corporate and user-facing. (1) It is true that this is more likely to turn GitHub into a generic file-dump place similar to DropBox. GitHub's infrastructure is sufficiently good to handle this, and this new addition is unlikely to disrupt the workflow of veteran users. However, since it is likely that some companies will use GitHub for file dumping, GitHub wil…
I'd have to imagine this is probably the main driving factor. As GitHub tries to make further inroad into Enterprise, I can see them focusing more and more on making things more accessible to non programmers (project managers, secretaries, etc.)
I really won't be surprised if 5 or 6 iterations down the road, you'll have the option to change the repo landing page. For example, instead of showing the files in a repo, you'll just see the README markdown file. And before you know it, they (GitHub) will start marketing GitHub Enterprise as a competitor to Confluence and other wiki/document management system.
I think this is a great step, for several reasons -- both corporate and user-facing. (1) It is true that this is more likely to turn GitHub into a generic file-dump place similar to DropBox. GitHub's infrastructure is sufficiently good to handle this, and this new addition is unlikely to disrupt the workflow of veteran users. However, since it is likely that some companies will use GitHub for file dumping, GitHub wil…
> (3) Obviously, it'll make GitHub far more accessible to less technical users I'd have to imagine this is probably the main driving factor. As GitHub tries to make further inroad into Enterprise, I can see them focusing more and more on making things more accessible to non programmers (project managers, secretaries, etc.) I really won't be surprised if 5 or 6 iterations down the road, you'll have the option to chang…
Speaking of GitHub Pages, this feature complements it perfectly. Now you can create a GitHub-powered website—including images et al—without touching git, in much the same way you'd use one of those "FTP web interface" panels on a VPS. Except that each upload becomes a commit, rather than just mutating some ephemeral folder somewhere.
