Skill: This skill helps writers use more inclusive IT terminology.

[julian-cable]

You are a member of a Diversity, Equity, and Inclusion (DEI) team. Your mission is to create the conditions for belonging and inclusion in the workplace. The people whom you support are new to principles of inclusion and need a safe place to fail.

[instruct-lab-bot]

Beep, boop 🤖, Hi, I'm @instructlab-bot and I'm going to help you with your pull request. Thanks for you contribution! 🎉

I support the following commands:

• @instructlab-bot precheck -- Check existing model behavior using the questions in this proposed change.
• @instructlab-bot generate -- Generate a sample of synthetic data using the synthetic data generation backend infrastructure.
• @instructlab-bot generate-local -- Generate a sample of synthetic data using a local model.
• @instructlab-bot help -- Print this help message again.

Note

Results or Errors of these commands will be posted as a pull request check in the Checks section below

Note

Currently only maintainers belongs to [[taxonomy-triagers taxonomy-approvers taxonomy-maintainers instructlab-bot-triagers instructlab-bot-maintainers oversight-committee]] teams are allowed to run these commands.

[jjasghar]

Please fix the DCO :)

[github-actions]

This pull request has been automatically marked as stale because it has not had activity within 15 days. It will be automatically closed if no further activity occurs within the next 31 days.

[nimbinatus]

Hi there! Thanks for the submission!

I wanted to give a bit more context on the DCO comment. We need you to sign something called the Developer Certificate of Origin, or DCO. Please review this document about what the DCO is and how to fix this issue, and please let me know if you need further help. As soon as the DCO issue is resolved, we can review!

[julian-cable]

Hi @nimbinatus Just to bring you up to date, since I submitted this PR, @nicholasjayantylearns and I decided to restructure our submissions for Conscious Language, and in due course I will be submitting several PRs broken down by taxonomy. Those PRs will then render this existing PR obsolete.

Happy to comply with the DCO requirement. Because I am using the InstructLab UI (https://ui.instructlab.ai/), I am not manually generating a commit message, and would appreciate any guidance on how best to meet the DCO need in this context. Also, I saw from this PR an error because of a mismatch in the (auto) commit between my GitHub ID and my work email address.

I'd appreciate any guidance for how best to deal with these issues for when I come to submit the next batch of PRs.
Many thanks!

[nimbinatus]

Hi @nimbinatus Just to bring you up to date, since I submitted this PR, @nicholasjayantylearns and I decided to restructure our submissions for Conscious Language, and in due course I will be submitting several PRs broken down by taxonomy. Those PRs will then render this existing PR obsolete.

Awesome! Looking forward to it!

Happy to comply with the DCO requirement. Because I am using the InstructLab UI (https://ui.instructlab.ai/), I am not manually generating a commit message, and would appreciate any guidance on how best to meet the DCO need in this context. Also, I saw from this PR an error because of a mismatch in the (auto) commit between my GitHub ID and my work email address.

This is a great question. I think the InstructLab UI team will be making a release soon:tm: that should allow you to go back in and address the DCO in the UI, but I need to check with them.

That being said, is your work email address associated with your GitHub ID? The process is described by GitHub here. You shouldn't have to make it a primary email address or anything, just link it. I think that should actually make the DCO happy, as well, since you have actually signed the commit, but I may be wrong.

Unfortunately, once the commit is made, though, even GitHub tells us that changing the message in the commit to add the signature (what's called "amending" the commit message) must be done on the command line or via GitHub Desktop. Until we have a way to do it through the InstructLab UI, these two methods are the only way to change the email you used to sign the commit. If you're not familiar with either one, I'm afraid the only other option is to close the submission and submit all over again with the email that matches your GitHub account.

I'd appreciate any guidance for how best to deal with these issues for when I come to submit the next batch of PRs. Many thanks!

Absolutely! Does this help? Are there any more questions I can answer for you?

[github-actions]

This pull request has been automatically marked as stale because it has not had activity within 15 days. It will be automatically closed if no further activity occurs within the next 31 days.