Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
85 commits
Select commit Hold shift + click to select a range
7d6421e
chore: Fix dictionaries
javierbrea Nov 14, 2024
c782dcd
chore: Add workflow test
javierbrea Nov 14, 2024
4012896
chore: Add shell option
javierbrea Nov 14, 2024
5341238
chore: Add dependency between jobs
javierbrea Nov 14, 2024
7d2f2a0
chore: Add dependency between targets
javierbrea Nov 14, 2024
173180a
chore: Add dependency between targets
javierbrea Nov 14, 2024
01f2908
chore: Build before linting
javierbrea Nov 14, 2024
e99e664
chore: Build dev dependencies before linting
javierbrea Nov 14, 2024
086ec09
chore: Run check:spell
javierbrea Nov 14, 2024
892f1c5
feat: Update cache
javierbrea Nov 14, 2024
4b5af5f
chore: Fix unable to update cache
javierbrea Nov 14, 2024
d64013d
chore: Add check:types step
javierbrea Nov 14, 2024
468767f
chore: Add dependency between jobs
javierbrea Nov 14, 2024
ae6f6a5
chore: Try storing cache in the same workflow
javierbrea Nov 14, 2024
ef23f07
chore: Try fixing the cache
javierbrea Nov 14, 2024
d4b4d0c
chore: Try using different cache keys
javierbrea Nov 14, 2024
7ce301d
chore: Add all targets
javierbrea Nov 14, 2024
8acac55
chore: Avoid nx rejecting cache
javierbrea Nov 14, 2024
e2e44d6
chore: reduce coverage threshold
javierbrea Nov 14, 2024
96804f3
chore: Rename jobs
javierbrea Nov 14, 2024
8d337dd
feat: Try saving cache
javierbrea Nov 14, 2024
ce9e966
chore: Try renaming cache
javierbrea Nov 14, 2024
0bc88f3
chore: Fix nx cache not working
javierbrea Nov 14, 2024
f8c0c84
chore: Fix nx cache not working
javierbrea Nov 14, 2024
0b54609
chore: Run only affected in PR
javierbrea Nov 14, 2024
7390a61
chore: Try using another cache with files hash
javierbrea Nov 14, 2024
63f42e6
chore: Remove commit cache
javierbrea Nov 14, 2024
afa9b42
test: Fix mermaid diagrams tests temporarily
javierbrea Nov 14, 2024
a0d4cb7
chore: Upgrade mermaid-cli library
javierbrea Nov 14, 2024
42bc82d
chore: Skip test and add TODO
javierbrea Nov 14, 2024
606e609
chore: Add dependency between jobs
javierbrea Nov 14, 2024
2dda2a7
chore: Add lint affected
javierbrea Nov 14, 2024
3794fea
chore: Try saving cache always
javierbrea Nov 14, 2024
77aa175
chore: Try not using ref name in cache
javierbrea Nov 14, 2024
a33f6e9
chore: Use simple cache action
javierbrea Nov 14, 2024
da672ce
chore: Use single job to run all targets
javierbrea Nov 14, 2024
29eb99c
chore: Run workflow
javierbrea Nov 14, 2024
367aaf6
chore: Run workflow
javierbrea Nov 14, 2024
59f8b18
test: Test save cache with single job
javierbrea Nov 14, 2024
3c4a80c
chore: Use simple cache
javierbrea Nov 14, 2024
6e9c368
chore: Delete cache to overwrite it
javierbrea Nov 14, 2024
3be5699
chore: Delete cache to overwrite it
javierbrea Nov 14, 2024
a9b2d87
chore: Use reusable action
javierbrea Nov 14, 2024
0390055
chore: Use reusable action
javierbrea Nov 14, 2024
b8a65b0
chore: Use reusable action
javierbrea Nov 14, 2024
e291294
chore: Try using github.token
javierbrea Nov 14, 2024
3e9ae6e
chore: Add shell
javierbrea Nov 14, 2024
59f7899
chore: Use reusable workflow
javierbrea Nov 14, 2024
cad0181
chore: Run in series
javierbrea Nov 14, 2024
21d8905
chore: Add change for testing caches
javierbrea Nov 14, 2024
82b2065
chore: Test markdown-conf-sync code change
javierbrea Nov 14, 2024
b89833c
chore: Restore files to its original state
javierbrea Nov 14, 2024
88a0a44
chore: Test another change in markdown-conf-sync test file
javierbrea Nov 14, 2024
77ff439
chore: Add PR workflow dispatch
javierbrea Nov 14, 2024
4206889
chore: Fix fetch depth for calculing affected
javierbrea Nov 14, 2024
9b9c452
chore: Use different cache for different branches
javierbrea Nov 14, 2024
ee52bb9
chore: Use different cache for different branches
javierbrea Nov 14, 2024
5517413
chore: Use different cache for different branches
javierbrea Nov 14, 2024
7093fa8
chore: Restore change for testing caches
javierbrea Nov 14, 2024
f7f6621
chore: Try reusing cache from other branches. Remove cache only from …
javierbrea Nov 14, 2024
e263184
chore: Fix caches
javierbrea Nov 14, 2024
86469d7
chore: Add more restore-keys to avoid problems with branch name prefixes
javierbrea Nov 14, 2024
1bd4aa9
chore: Prepare child-process-manager for publishing
javierbrea Nov 15, 2024
e0cf9c5
chore: Fix lint
javierbrea Nov 15, 2024
9a06a92
chore: Add license to confluence-sync
javierbrea Nov 15, 2024
da8c6cc
docs: Update confluence-sync docs
javierbrea Nov 15, 2024
7332820
docs: Update confluence-sync docs
javierbrea Nov 15, 2024
3f116a8
docs: Update confluence-sync docs
javierbrea Nov 15, 2024
9c6275b
docs: Fix admonitions
javierbrea Nov 15, 2024
c8d5f31
chore: Change confluence-sync description. Add license to files
javierbrea Nov 15, 2024
b1401b9
docs: Change title
javierbrea Nov 15, 2024
64be035
chore: Ignore non-production files to build markdown-confluence-sync
javierbrea Nov 15, 2024
b361fb4
chore: Define input dependencies before package inputs to override po…
javierbrea Nov 15, 2024
b584846
chore: Add license to markdown-confluence-sync
javierbrea Nov 18, 2024
6cce442
docs: markdown-confluence-sync docs
javierbrea Nov 18, 2024
5a8c507
docs: Add link to Docusaurus
javierbrea Nov 18, 2024
539e5b0
docs: Add alternatives
javierbrea Nov 18, 2024
a26e947
docs: Add cspell and eslint config readme files and license files
javierbrea Nov 18, 2024
1a96879
docs: Add main contributing file docs
javierbrea Nov 18, 2024
0bf97e1
chore: Lint and check:spell root files
javierbrea Nov 18, 2024
dfaf428
chore: Revert wrong automatic change
javierbrea Nov 18, 2024
0e79156
fix: Remove unneded conditional
javierbrea Nov 18, 2024
fc5e46d
chore: Upload unit tests coverage report
javierbrea Nov 18, 2024
fa255b3
chore: Add publish pipeline
javierbrea Nov 18, 2024
40bcc44
chore: Change publish event type
javierbrea Nov 18, 2024
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions .github/CLA.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# Contributor License Agreement

# Table of Contents

- [Why Require a CLA?](#why-require-a-cla)
- [Legal Terms and Agreement](#legal-terms-and-agreement)

# Why Require a CLA?
Agreeing to a CLA explicitly states that you are entitled to provide a contribution, that you cannot withdraw permission to use your contribution at a later date, and that Telefónica Innovación Digital has permission to use your contribution in our commercial products.

This removes any ambiguities or uncertainties caused by not having a CLA and allows users and customers to confidently adopt our projects. At the same time, the CLA ensures that all contributions to our open source projects are licensed under the project's respective open source license, such as Apache 2.0, MPL2 or MIT.

Requiring a CLA is a common and well-accepted practice in open source. Major open source projects require CLAs such as Apache Software Foundation projects, Facebook projects (such as React), Google projects (including Go), Python, Django, and more. Each of these projects remains licensed under permissive OSS licenses such as MIT, Apache, BSD, and more.

Signing the CLA
Open a pull request ("PR") to any of our projects to sign the CLA. A bot will comment on the PR asking you to sign the CLA if you haven't already.

Follow the steps given by the bot to sign the CLA. This will require you to log in with GitHub (we only request public information from your account) and to add a comment to the PR. We will store your Github user name in a branch in this repository. We will only use this information for CLA tracking; none of your information will be used for marketing purposes.

You only have to sign the CLA once. Once you've signed the CLA, future contributions to any Telefónica Innovación Digital project will not require you to sign again.

# Legal Terms and Agreement
In order to clarify the intellectual property license granted with Contributions from any person or entity, Telefónica Innovación Digital, Inc. ("Telefónica Innovación Digital") must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license does not change your rights to use your own Contributions for any other purpose.

You accept and agree to the following terms and conditions for Your present and future Contributions submitted to Telefónica Innovación Digital. Except for the license granted herein to Telefónica Innovación Digital and recipients of software distributed by Telefónica Innovación Digital, You reserve all right, title, and interest in and to Your Contributions.

Definitions. "You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with Telefónica Innovación Digital. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is or previously has been intentionally submitted by You to Telefónica Innovación Digital for inclusion in, or documentation of, any of the products owned or managed by Telefónica Innovación Digital (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to Telefónica Innovación Digital or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Telefónica Innovación Digital for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."

Grant of Copyright License. Subject to the terms and conditions of this Agreement, You hereby grant to Telefónica Innovación Digital and to recipients of software distributed by Telefónica Innovación Digital a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.

Grant of Patent License. Subject to the terms and conditions of this Agreement, You hereby grant to Telefónica Innovación Digital and to recipients of software distributed by Telefónica Innovación Digital a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.

You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that you will have received permission from your current and future employers for all future Contributions, that your applicable employer has waived such rights for all of your current and future Contributions to Telefónica Innovación Digital, or that your employer has executed a separate Corporate CLA with Telefónica Innovación Digital.

You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.

You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON- INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.

Should You wish to submit work that is not Your original creation, You may submit it to Telefónica Innovación Digital separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".

You agree to notify Telefónica Innovación Digital of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect.
132 changes: 132 additions & 0 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,132 @@

# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the overall
community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or advances of
any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email address,
without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official email address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at [email protected].
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within the
community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
Loading
Loading