-
Notifications
You must be signed in to change notification settings - Fork 228
Twitter Bot
Anisa Hawes edited this page Dec 7, 2022
·
2 revisions
A Twitter bot was built for The Programming Historian by @walshbr.
This repository contains the code https://github.com/programminghistorian/proghistbot alongside some general information in the README.md about how it works, and what services it is integrated with.
When a lesson is retired, its associated tweets must also be removed from the spreadsheet. These edits should be made by the editor who merges the pull request to retire the lesson. Once the pull request is merged, the process for removing them is pretty straightforward:
- On the spreadsheet, go to the tab for language of the publication from which the lesson is being retired.
- Select the entire row of the lesson tweet that needs to be removed and copy it to your clipboard.
- Paste the copied data as a new row onto the last tab of the spreadsheet entitled "deprecated." This tab is not used by the bot and only serves as an archive of past tweets.
- Now that you've archived the tweet, you can safely remove it from the spreadsheet. Go back to the language tab for the tweet, highlight the row in question, and delete the row. This step is especially important - make sure that you don't just clear the data and leave a blank row in its place. You want the old row entirely removed so that there are no blank rows in data.
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees