Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge main into v7.1 #546

Merged
merged 30 commits into from
Sep 3, 2024
Merged

Merge main into v7.1 #546

merged 30 commits into from
Sep 3, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 3, 2024

Copy changes from main to v7.1
This PR is auto-generated by [gh pr create].

github-actions bot and others added 27 commits March 8, 2024 08:54
Co-authored-by: Luther Tychonievich <[email protected]>
* decribe branches in README.md

* Update README.md

Co-authored-by: Dave Thaler <[email protected]>

---------

Co-authored-by: Dave Thaler <[email protected]>
Per discussion in steering committee meeting 2024-04-04, using <https://gedcom.io/community/> as the contact info because that page describes various means of contact and is expected to be updated from time to time as means of contact change.
* Add CI/CD workflow to validate YAML files

Signed-off-by: Dave Thaler <[email protected]>

* Update YAML files to resolve yamllint errors

Signed-off-by: Dave Thaler <[email protected]>

* Update .github/workflows/validate-yaml.yml

* Update .github/workflows/validate-yaml.yml

---------

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Avoid validating the same file multiple times

https://github.com/FamilySearch/GEDCOM/actions/runs/8838156091/job/24268618756
under "Validate YAML" shows multiple occurences of files under
.github/workflow since .github and .github/workflow are both passed to
yamllint

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
* Add Separation event

* Remove FS API reference
https://github.com/FamilySearch/GEDCOM/actions/runs/9044561163 failure
reports: "The workflow is not valid.
.github/workflows/propagate-main-to-v7.1.yml (Line: 18, Col: 3): The
identifier 'merge-to-v7.1' is invalid. IDs may only contain alphanumeric
characters, '_', and '-'. IDs must start with a letter or '_' and and
must be less than 100 characters."

This PR therefore removes the '.' that is causing the failure.

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Related to PR #459 which tracks the separation event

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Fixes #465

Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
* Add the meaning of WWW

Previously (in both 5.5.1 and 7.0.0–7.0.14) `WWW` was defined only by the type of is payload. This is an attempt to fix that without invalidating any existing files.

Resolves #476

* Update specification/gedcom-3-structures-3-meaning.md

Co-authored-by: Dave Thaler <[email protected]>

---------

Co-authored-by: Dave Thaler <[email protected]>
* Define "principle date"

As pointed out in #488 and #490, the definition of DATE includes the vague phrase "principle date" which could use some clarification. This is my effort to provide that clarification.

Note, if competing definitions of the principle date in these contexts exists then this suggestion could be seen as backwards-incompatible and may need to be reworded as a non-normative recommendation or note. That said, I'm not aware of any conflicting definitions.

Resolves #490

* typos

* typo
Co-authored-by: Luther Tychonievich <[email protected]>
* Clarify nickname

Add additional clarification to nickname, explaining the word's meaning in English which is not shared by several European countries. See [this comment](#473 (comment)) and the rest of issue #473 for more on why this clarification is needed.

Although #473's discussion covers many more topics, if we go back to the title and first question in the issue I think this resolves #473.

* Update specification/gedcom-3-structures-3-meaning.md

* Change recommendation

* Update specification/gedcom-3-structures-3-meaning.md

* Update specification/gedcom-3-structures-3-meaning.md

---------

Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Luther Tychonievich <[email protected]>
* Restore 3.0's definition of jurisdiction

Restored the definition of "jurisdiction" that was present in version 3.0.

Resolved #496

* Update specification/gedcom-3-structures-3-meaning.md

Additional examples and less proscriptive text
Co-authored-by: Luther Tychonievich <[email protected]>
* Increase largest PLAC example

resolves #512

* Update specification/gedcom-3-structures-3-meaning.md
Co-authored-by: Luther Tychonievich <[email protected]>
Signed-off-by: Dave Thaler <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Luther Tychonievich <[email protected]>
* Update changelog.md

We've been making changes without updating the changelog. This summarizes the changes since v7.14 was released.

* Update changelog.md

* Update changelog.md

---------

Co-authored-by: Dave Thaler <[email protected]>
* EXID.TYPE for BillionGraves.com and WikiTree identifiers

Fixes #539

* Update exid-types.json

Co-authored-by: Luther Tychonievich <[email protected]>

* Apply suggestions from code review

Co-authored-by: Luther Tychonievich <[email protected]>

---------

Co-authored-by: Dave Thaler <[email protected]>
Co-authored-by: Luther Tychonievich <[email protected]>
Co-authored-by: Dave Thaler <[email protected]>
* Update exid-types.json

Resolve incorrect URIs as noted in #539

* move /name

* move /name

* move /name

* move /name
@dthaler dthaler merged commit cefdaa8 into v7.1 Sep 3, 2024
1 check passed
@dthaler dthaler deleted the merge-main-into-v7.1 branch September 3, 2024 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr Automated PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants