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

Fix warnings from GHA checks #2

Merged
merged 40 commits into from
Aug 17, 2023
Merged

Fix warnings from GHA checks #2

merged 40 commits into from
Aug 17, 2023

Conversation

spier
Copy link

@spier spier commented Aug 16, 2023

Hi @magawande,

this PR is doing two things:

  • patching your branch with any changes that happened to InnerSourcePatterns:main since you branched out (this was a couple of months ago, so just want to make sure that we had no possible merge conflicts here)
  • fixing a link found by Link Check PR
  • making some changes so that the "Spelling & Styles" won't trhow warnings on the author names in your new pattern any more

Btw I had to us this "fork from your fork" approach as GitHub doesn't allow me to push to branches created on an organization-owned fork. Learned something new today!

Once your merge this PR, the checks on InnerSourceCommons#573 should run again, and will hopefully all be green then.

spier and others added 30 commits May 12, 2023 11:05
* Script to identify upgradeable patterns based on their number of Known Instances
* Formatting changes to the 'Known Instances' section of some patterns. Allows for easier scanning of the new find_upgradeable_patterns.rb script
…as a term, changed formatting, shortened name (InnerSourceCommons#409)

* Moved to InnerSource as a term, changed formatting, shortened name

I believe this pattern does need a bit of love. I only made some first changes to the name "InnerSource", changed some formatting and shortened the name.

However I believe the solutions given are incomplete in particular wrt. build chain solutions to the issue. It might make sense to mention explicit release naming and numbering schemes. It might make sense to mention the option of setting up build systems to trigger new builds on upstream code changes or upstream releases.

* Spell out definition of SCM and add a link

---------

Co-authored-by: Sebastian Spier <[email protected]>
* Add vale.
* Fixes to the spelling, discovered by our new spellchecker. Mostly fixes in the Structured patterns, some for the Initial patterns as well.
* Move config for pattern syntax linting to .github
* Explain spellchecking approach in the Contributor Handbook
…SourceCommons#550)

Airbus switched from SAP portal to Backstage/Bazaar as Backstage is becoming the standard internally
Co-authored-by: bakisunsan <[email protected]>
Create COMMUNICATION-template.md - Creating template so I have link to add to the base documentation pattern when I add the template to it.

---------

Co-authored-by: Sebastian Spier <[email protected]>
…ing-extensions-for-sustainable-growth-ja-translation

Japanese Translation - Extensions for Sustainable Growth Pattern
* Use glob to select files to be checked by vale
* Removing GH token
* Remove unused gitignore rule
* Adding debug flag, to increase inspectability of vale output in future GHA runs
dependabot bot and others added 10 commits August 2, 2023 23:38
…ceCommons#558)

Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2.
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md)
- [Commits](npm/node-semver@v5.7.1...v5.7.2)

---
updated-dependencies:
- dependency-name: semver
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Adding configuration for the welcome bot.
* Update link to the ISC slack instance.
* Stop checking link to chatham house rule (as it always gets reported as broken, even though it is not).
Move Release Process to structured by doing various changes:

* Update title
* Update problem category (in the mindmap). Also added Standard Base Documentation to this new problem category.
* Updates to Context and Force. Plus a few grammar clean ups
* Update Patlet
* Restructure Problem and Context
This also fixes an issue reported by 'Link Check PR'.

Merge branch 'main' into adding-new-feature-owner-pattern
@magawande
Copy link

magawande commented Aug 16, 2023 via email

@magawande magawande merged commit ffd84d9 into fidelity-contributions:adding-new-feature-owner-pattern Aug 17, 2023
@spier spier deleted the adding-new-feature-owner-pattern branch August 18, 2023 06:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants