Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Can you use mercurial patch queues with BitBucket after it has got it's new design?
Before you could press on the "Patch queue" link in a repository to create a patch queue, but that link seems to be gone now. Am I missing something?
I am using mercurial to manage a set of patches I need to run some software on my own machines, in short the method outlined here. I've been using this method for some time and I've also wondered if there's an easier way to do it with git?
It seems that patch queues are treated as forks in Bitbucket now. To create a patch queue click on the Fork button then click on the create a patch queue link on the top right of the fork page.
You can then administer the patch queue by clicking on the Fork link on the Overview page and managing it as you would any other repository.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 days ago.
Improve this question
For a some time now I'm thinking about a way to setup a continuous delivery pipeline and don't seem to get my head around it.
I want to auto-create a Github release with a corresponding tag. Plus I want to update the version in a file inside the repo (/docs/antora.yml). The version in the antora.yml should be the same as the tag which I want to create.
Since the source of truth always is the main branch on Github I only want to create tags in the remote repo. Tagging locally and pushing the tag to the remote repo is not an options! Ideally I would like a successful Pull Request to be the trigger. But (as far as I understand) then I always have to create a branch. Plus I don't want every PR into main to create a new release and tag. I want to handpick the PRs.
One way to achieve this would be to create a dedicated release/v1.2.3 branch, run everything from there and auto-create a tag and release. Then a release pipeline could listen to the tag-creation and do the actual e.g. deployment to DockerHub.
What I don't like about this is, that I need a release-branch which kind of moves me further away from working trunk-based. And I need two pipelines: a CD-pipeline which would only handle organizational stuff and a release-pipeline which does the technical deployments.
I would prefer to do everything in a single CD pipeline based on the main branch.
Now I'm very interested in your opinions. Are my thoughts valid or is this some kind of anti-pattern? Do you know some best practices? Maybe someone has an example implementation? I think I can handle writing the actual pipeline code. I'm just not sure how to organize my process. By the way: I already have a CI pipeline working. So to me CD is the logical next step
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I am developing a website for a company. However some of the css attributes which are in my project goes missing when I commit my code to the subversion repository.
So in the other end when my team mates access it, the attributes goes missing. I reassured that it was not a mistake when I commit. How can I resolve this?
Subversion commits are atomic and consistent. If some files are missing, then they were not included in your commit or were not even added to your working copy with the svn add command.
When you put new files to your working copy, you first need to tell Subversion client to begin tracking them, i.e. add them to the working copy. You need to do this using the svn add command.
Before you commit, you need to examine the status of your working copy with the svn status command. It will help you find out whether there are any unversioned files or irrelevant changes.
Read SVNBook | Basic Work Cycle.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I would like to display a code snippet from my own public GitHub source repo in my own web site, without having to make a copy. This is for a tutorial to illustrate some programming concepts. So not to run it but to pretty print it, as it were.
I bet this is something that many people need. I am looking for a lead on how to do this.
You could use the GitHub API to accomplish this.
See the Get Contents endpoint.
Yes, you can do that either by publishing your repo on npm and then referring it as npm dependency in projects package.json.
or 2nd , you can directly refer GitHub repo as dependency in package.json.
Hope this gets you in right direction.
thanks
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am really thinking of how I can build a very minimal Git-like software only for my self for now!
I have gone through Git documentations and even the way git works and I have quite an understanding on it.
Is there any example for me to study as a bonus before I dive into this project?.
In addition to the Documentation/technical folder which explains the internals of Git, you can study how Git was re-implemented, as an exercice, in other languages.
See for instance:
in Go the project src-d/go-git (recent 2018),
in Javascript: danlucraft/git.js (much older),
In Javascript (more recent 2015): Gitlet.
In Java, the project eclipse/jgit (used by EGit)
In C (with a lot of bindings for other languages), LibGit2 (and its GitHub repository, apologies to Edward Thomson for not mentioning it first.)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I'm completely new to Git, and one question I have that I cannot seem to find an answer to is this: when building a website is there any advantage to using private repositories vs public? I'm not referring to developing web-apps or other proprietary information so-to-speak, just basic web development. For example I would like to learn to use git (github) by updating our current website. Since source code is viewable to all, what advantages would be gained by using a private repository?
Thanks in advance!
If you are just developing in html/css/javascript(frontend), that is all viewable to the client. If you start to use server side scripting, (i.e PHP) you may have more sensitive data that you do not want public. You can also use git as a local repository and not have anything on github. That will handle source control and will all be kept local to the machine it is on. If you are developing on a server that other people use, they can also have access to edit that local repository.
Here is a good page for how to set up a local repository.