In the introduction it states "It is widely used, both because it’s easy to set up and because of a hosting site called Bitbucket." Bitbucket no longer host Mercurial repos and so this should probably be changed to "It is widely used and it’s easy to set up."

In the "Hosting" section it probably should be made clear that some of these services host both git and hg but some only host git repos. Below is a suggested change - I have added a sentence in the middle.
"Each of these services provides a web interface that enables people to create, view, and edit their code repositories. Some host Git and Mercurial repositories, some host only Git repositories. These services also provide communication and project management tools including issue tracking, wiki pages, email notifications, and code reviews."

The Mercurial site has changed from http://mercurial.selenic.com/ to https://www.mercurial-scm.org/ and the former does not re-direct, so any links that contain it are broken.

make lesson-check reports:

Unexpected image files: bitbucket-find-repo-string.png, hg-after-change-to-duplicate-repo.svg, hg-after-duplicate-clone.svg, hg-after-first-conflicting-change.svg, hg-after-merging.svg, hg-after-pulling-to-local-repo.svg, hg-after-second-conflicting-change.svg, hg-freshly-made-bitbucket-repo.svg, hg-kdiff3-conflict-windows-resolved.png, hg-kdiff3-conflict-windows.png

Please use this issue for discussion of changes we should make by mid-Jun 2016.

Split 04-open into 3 files -open, -licensing, and -hosting, and elaborate the discussions in each similar to what has been done in swcarpentry/git-novice/08-open, swcarpentry/git-novice/09-licensing, and swcarpentry/git-novice/10-hosting.

In https://swcarpentry.github.io/sql-novice-survey/06-agg/

[What does this query do?] In order to find the differences of individual readings with the individual's average reading, I think we'd require nesting the query in the following manner:

SELECT S.* , AV.avg_reading , S.reading - AV.avg_reading AS diff_reading FROM Survey S INNER JOIN (SELECT person, quant, AVG(reading) AS avg_reading FROM Survey GROUP BY person, quant) AV ON S.person = AV.person AND S.quant = AV.quant ;

At this stage, nesting is not introduced, and I think nesting deserves a new section by itself given its usefulness.

I think the next question [Ordering When Concatenating] also has the same issue (requires nesting).

The lesson infrastructure committee unanimously approved the proposal of using the same set of labels across all our repositories during its last meeting on May 23rd, 2018.

This repository has now been converted to use the standard set of labels.

If this repository used the previous set of recommended labels by Software Carpentry, they have been converted to the new one using the following rules:

The label instructor-training was removed as it is not used in the workflow of certifying new instructors anymore. The label question was left as is when it was in use, and removed otherwise. If your repository used custom labels (and issues were flagged with these labels), they were left as is.

The lesson infrastructure committee hopes the standard set of labels will make it easier for you to manage the issues you receive on the repositories you manage.

The lesson infrastructure committee will evaluate how the labels are being used in the next few months and we will solicit your feedback at this stage. In the meantime, if you have any questions or concerns, please leave a comment on this issue.

-- The Lesson Infrastructure subcommittee

PS: we will close this issue in 30 days if there is no activity.

If your Maintainer team has decided not to participate in the June 2019 lesson release, please close this issue.

To have this lesson included in the 18 June 2019 release, please confirm that the following items are true:

• Example code chunks run as expected
• Challenges / exercises run as expected
• Challenge / exercise solutions are correct
• Call out boxes (exercises, discussions, tips, etc) render correctly
• A schedule appears on the lesson homepage (e.g. not “00:00”)
• Each episode includes learning objectives
• Each episode includes questions
• Each episode includes key points
• Setup instructions are up-to-date, correct, clear, and complete
• File structure is clean (e.g. delete deprecated files, insure filenames are consistent)
• Some Instructor notes are provided
• Lesson links work as expected

When all checkboxes above are completed, this lesson will be added to the 18 June lesson release. Please leave a comment on carpentries/lesson-infrastructure#26 or contact Erin Becker with questions ([email protected]).

See swcarpentry/shell-novice#552

The 'Recovering old versions' section suggests using revert to return to a historical revision. It first suggests using revert to handle a mistaken change in the working directory, but then goes on to suggest revert as a general mechanism for returning to an arbitrary earlier revision. I think this is not the intended use of revert, and that recommending update would be better.

Rationale:

• The mercurial documentation for revert starts with a Note saying ‘To check out earlier revisions, you should use "hg update REV". To cancel an uncommitted merge (and lose your changes), use "hg update --clean .".’
• The same documentation mentions the -r option only in the context of indicating which of two parents should be reverted to (as opposed to arbitrary older revisions).
• The current snapshot of the Mercurial book seems to describe revert solely in the context of fixing mistakes.

Thus my impression is that revert is a relatively ‘advanced’ Mercurial command, intended only for fixing mistakes. It's useful to mention it, but perhaps only for the special case of immediate fixing of a mistaken edit. It might usefully come as a final remark to a ‘Recovering old versions’ page which primarily discusses update.

On the couple of occasions when I've taught this Mercurial lesson, I've told the class to use update in this case, and specifically not to use revert.

I could offer a pull request for redrafted the text if that would seem useful.

Please, consider adding a lesson topic to the repository. To do so you can follow the help about how to add topics to the repository. Check out the topics that the Genomics R intro lesson has gotten to add others that may be relevant to this lesson.

This will help people to know which repositories are lessons and also could be used to automate analysis of the repositories.