Mark boolean values consistently as code element

Author: mschoettle

README.md

@@ -86,7 +86,7 @@ Leave it null for the first run of the script. Then the script will show you whi
 
 #### gitlab.listArchivedProjects
 
-When listing projects on the first run (projectID = null), include archived ones too. The default is *true*.
+When listing projects on the first run (projectID = null), include archived ones too. The default is `true`.
 
 #### gitlab.sessionCookie
 
@@ -108,25 +108,25 @@ Under which organisation or user will the new project be hosted
 
 #### github.ownerIsOrg
 
-A boolean indicator (default is *false*) to specify that the owner of this repo is an Organisation.
+A boolean indicator (default is `false`) to specify that the owner of this repo is an Organisation.
 
 #### github.token
 
 Go to [Settings / Developer settings / Personal access tokens](https://github.com/settings/tokens). Generate a new token with `repo` scope and copy that into the `settings.ts`
 
 #### github.token_owner
 
-Set to the user name of the user whose token is used (see above). This is required to determine whether the user running the migration is also the creator of comments and issues. If this is the case and `useIssueCreationAPI` is true (see below), the extra line specifying who created a comment or issue will not be added.
+Set to the user name of the user whose token is used (see above). This is required to determine whether the user running the migration is also the creator of comments and issues. If this is the case and `useIssueCreationAPI` is `true` (see below), the extra line specifying who created a comment or issue will not be added.
 
 #### github.repo
 
 What is the name of the new repo
 
 #### github.recreateRepo
 
-If true (default is false), we will try to delete the destination github repository if present, and (re)create it. The github token must be granted `delete_repo` scope. The newly created repository will be made private by default.
+If `true` (default is `false`), we will try to delete the destination github repository if present, and (re)create it. The github token must be granted `delete_repo` scope. The newly created repository will be made private by default.
 
-If you've set `github.recreateRepo` to true and the repo belongs to an Organisation, the `github.ownerIsOrg` flag **must** be set as true.
+If you've set `github.recreateRepo` to `true` and the repo belongs to an Organisation, the `github.ownerIsOrg` flag **must** be set as `true`.
 
 This is useful when debugging this tool or a specific migration. You will always be prompted for confirmation.
 
@@ -160,7 +160,7 @@ When one renames the project while transfering so that the projects don't loose
 
 #### conversion.useLowerCaseLabels
 
-If this is set to true (default) then labels from GitLab will be converted to lowercase in GitHub.
+If this is set to `true` (default) then labels from GitLab will be converted to lowercase in GitHub.
 
 #### conversion.addIssueInformation
 
@@ -170,57 +170,57 @@ If this is set to `true` (default) then issues and pull requests will get inform
 
 #### transfer.milestones
 
-If this is set to true (default) then the migration process will transfer milestones.
+If this is set to `true` (default) then the migration process will transfer milestones.
 
 #### transfer.labels
 
-If this is set to true (default) then the migration process will transfer labels.
+If this is set to `true` (default) then the migration process will transfer labels.
 
 #### transfer.issues
 
-If this is set to true (default) then the migration process will transfer issues.
+If this is set to `true` (default) then the migration process will transfer issues.
 
 #### transfer.mergeRequests
 
-If this is set to true (default) then the migration process will transfer merge requests.
+If this is set to `true` (default) then the migration process will transfer merge requests.
 
 #### transfer.releases
 
-If this is set to true (default) then the migration process will transfer releases.
+If this is set to `true` (default) then the migration process will transfer releases.
 Note that github api for releases is limited and hence this will only transfer the title and description of the releases
 and add them to github in chronological order, but it would not preserve the original release dates, nor transfer artefacts or assets.
 
 ### dryRun
 
-As default it is set to false. Doesn't fire the requests to github api and only does the work on the gitlab side to test for wonky cases before using up api-calls
+As default it is set to `false`. Doesn't fire the requests to github api and only does the work on the gitlab side to test for wonky cases before using up api-calls
 
 ### exportUsers
 
-If this is set to true (default is false) then a file called "users.txt" wil be created containing all
+If this is set to `true` (default is `false`) then a file called "users.txt" wil be created containing all
 usernames that contributed to the repository. You can use this with dryRun when you need to map users
 for the migration, but you do not know all the source usernames.
 
 ### useIssueImportAPI
 
-Set to true (default) to enable using the [GitHub preview API for importing issues](https://gist.github.com/jonmagic/5282384165e0f86ef105). This allows setting the date for issues and comments instead of inserting an additional line in the body.
+Set to `true` (default) to enable using the [GitHub preview API for importing issues](https://gist.github.com/jonmagic/5282384165e0f86ef105). This allows setting the date for issues and comments instead of inserting an additional line in the body.
 
 ### usePlaceholderIssuesForMissingIssues
 
-If this is set to true (default) then the migration process will automatically create empty dummy issues for every 'missing' GitLab issue (if you deleted a GitLab issue for example). Those issues will be closed on Github and they ensure that the issue ids stay the same on both GitLab and Github.
+If this is set to `true` (default) then the migration process will automatically create empty dummy issues for every 'missing' GitLab issue (if you deleted a GitLab issue for example). Those issues will be closed on Github and they ensure that the issue ids stay the same on both GitLab and Github.
 
 #### usePlaceholderMilestonesForMissingMilestones
 
-If this is set to true (default) then the migration process will automatically create empty dummy milestones for every 'missing' GitLab milestone (if you deleted a GitLab milestone for example). Those milestones will be closed on Github and they ensure that the milestone ids stay the same on both GitLab and Github.
+If this is set to `true` (default) then the migration process will automatically create empty dummy milestones for every 'missing' GitLab milestone (if you deleted a GitLab milestone for example). Those milestones will be closed on Github and they ensure that the milestone ids stay the same on both GitLab and Github.
 
 #### useReplacementIssuesForCreationFails
 
-If this is set to true (default) then the migration process will automatically create so called "replacement-issues" for every issue where the migration fails. This replacement issue will be exactly the same, but the original description will be lost. In the future, the description of the replacement issue will also contain a link to the original issue on GitLab. This way, users who still have access to the GitLab repository can still view its content. However, this is still an open task. (TODO)
+If this is set to `true` (default) then the migration process will automatically create so called "replacement-issues" for every issue where the migration fails. This replacement issue will be exactly the same, but the original description will be lost. In the future, the description of the replacement issue will also contain a link to the original issue on GitLab. This way, users who still have access to the GitLab repository can still view its content. However, this is still an open task. (TODO)
 
 It would of course be better to find the cause for migration fails, so that no replacement issues would be needed. Finding the cause together with a retry-mechanism would be optimal, and will maybe come in the future - currently the replacement-issue-mechanism helps to keep things in order.
 
 ### useIssuesForAllMergeRequests
 
-If this is set to true (default is false) then all merge requests will be migrated as GitHub issues (rather than pull requests). This can be
+If this is set to `true` (default is `false`) then all merge requests will be migrated as GitHub issues (rather than pull requests). This can be
 used to sidestep the problem where pull requests are rejected by GitHub if the feature branch no longer exists or has been merged.
 
 ### filterByLabel
@@ -242,7 +242,7 @@ Suggested values:
 
 ### mergeRequests
 
-Object consisting of `logfile` and `log`. If `log` is set to true, then the merge requests are logged in the specified file and not migrated. Conversely, if `log` is set to false, then the merge requests are migrated to GitHub and not logged. If the source or target branches linked to the merge request have been deleted, the merge request cannot be migrated to a pull request; instead, an issue with a custom "gitlab merge request" tag is created with the full comment history of the merge request.
+Object consisting of `logfile` and `log`. If `log` is set to `true`, then the merge requests are logged in the specified file and not migrated. Conversely, if `log` is set to `false`, then the merge requests are migrated to GitHub and not logged. If the source or target branches linked to the merge request have been deleted, the merge request cannot be migrated to a pull request; instead, an issue with a custom "gitlab merge request" tag is created with the full comment history of the merge request.
 
 ### usermap