Archive for the ‘Source Code Management’ Category
Posted by jpluimers on 2018/12/20
[WayBack] About Blocks – bl.ocks.org is so cool:
Bl.ocks (pronounced “Blocks”) is a simple viewer for sharing code examples hosted on GitHub Gist.
…
The main source for your example is in index.html. This file can contain relative links to other files in your Gist, such as images, scripts or stylesheets. And of course you can use absolute links, such as CDN-hosted D3, jQuery or Leaflet. To explain your example, add a README.md written in Markdown. (You can omit the index.html if you just want to write, too.)
[WayBack] Code-only-Blocks are cool too:
When your Gist is missing an index.html file, will hide the example iframe but continue to display everything else.
Just compare these:
–jeroen
Posted in Development, DVCS - Distributed Version Control, gist, GitHub, jQuery, Scripting, Software Development, Source Code Management, Web Development | Leave a Comment »
Posted by jpluimers on 2018/12/18
One of the BitBucket features I like a lot is that in the commit history, you see the branches involved in a nice diagram on the left side of the commits: https://bitbucket.org/pypy/pypy/commits
BitBucket used to be popular to host public repositories, but from a public perspective, they are on the decline for that (they even removed the [once popular] bitbucket.org/explore page and [WayBack] will not re-introduce it).
Right now, only major git based hosters still have explore pages:
So it makes sense to see where they provide diagrams of branches, so here are some examples to go from a project to the graph:
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/12/15
gmaster is an interesting Windows based git client, but you cannot install it off-line, and by default it does not use the external git.exe.
See the below tweets.
–jeroen
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, PlasticSCM, Software Development, Versioning | Leave a Comment »
Posted by jpluimers on 2018/12/14
If you want to add ignored files in Pastic SCM, there is no --force option like for instance git has. The only way is to:
- edit the
ignore.conf file so the affected files are not ignored any more
- add the affected files
- undo the
ignore.conf change
- check-in the changes
Source: [WayBack] plasticscm – Plastic SCM: Add ignored file – Stack Overflow
—jeroen
Posted in Development, PlasticSCM, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/12/06
Try https://gitlab.com/api/v4/users?username=??? where ??? is your username. This will only work if you are already logged into gitlab.
Alternatively,
- go to https://gitlab.com/profile/account and copy your Private token.
- Then run the following command from a bash-like terminal:
curl --header "PRIVATE-TOKEN: AAAA" https://gitlab.com/api/v4/users?username=BBBB
where AAAA is your private token and BBBB is your username.
Source: [WayBack] [solved]Where is my user ID in GitLab.com? – HowTo – GitLab Community Forum
Works:
- https://gitlab.com/users/sign_in
- https://gitlab.com/api/v4/users?username=wiert
Via the ID, you can find the issues assigned to the user:
–jeroen
Posted in Development, DVCS - Distributed Version Control, GitLab, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/11/26
[WayBack] Protected Branches | GitLab usually are a cool feature, but sometimes they get in the way, for instance when someone having enough rights has pushed credentials or API keys to a repository.
Unlike the picture in the documentation that indicates the default looks like Masters, this is now assigned to the role Maintainers.
Wrong:
Right:
More reading:
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, GitLab, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/11/20
When creating a library of libraries where the libraries use parts of the other libraries creates a mess when organised as a repository with subrepositories having other subrepositories.
It might be better to have one big repository containing a suite of functionality. This is why darkThreading became part of darkGlass: [WayBack] Why no git submodules for the libraries it depends on? · Issue #1 · chapmanworld/darkThreading · GitHub:
You might want to maintain that suite as one big versioned repository, with a different means of structuring it than a tree of submodules. That way you can keep the more complex interdependencies between the parts you have now.
Example of the mess: [WayBack] Duplicate submodules with Git – Stack Overflow
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 