Getting started with HTML - Learn web development If you look at code for a lot of other sites, you might come across a number of strange markup styles, including attribute values without quotes. This is permitted in certain circumstances, but it can also break your markup in other circumstances. The element in the code snippet below, <a>, is called an anchor. <a href= website</a> Anchors can also have a title attribute, a description of the linked page. <a href= title=The Mozilla homepage>favorite website</a> As written above, the browser misinterprets the markup, mistaking the title attribute for three attributes: a title attribute with the value The, and two Boolean attributes, Mozilla and homepage. Always include the attribute quotes.
GitHub - k88hudson/git-flight-rules: Flight rules for git - a work in progress! Webhooks Webhooks allow you to build or set up integrations which subscribe to certain events on GitHub.com. When one of those events is triggered, we'll send a HTTP POST payload to the webhook's configured URL. Webhooks can be used to update an external issue tracker, trigger CI builds, update a backup mirror, or even deploy to your production server. You're only limited by your imagination. Each webhook can be installed on an organization or a specific repository. You can create up to 20 webhooks for each event on each installation target (specific organization or specific repository). Events When configuring a webhook, you can choose which events you would like to receive payloads for. Each event corresponds to a certain set of actions that can happen to your organization and/or repository. The available events are: Wildcard Event We also support a wildcard (*) that will match all supported events. Payloads Each event type has a specific payload format with the relevant event information.
Reminders Reminders Reminders can be set on individual notes in a user’s Evernote account and allow the user to: Receive alerts at a pre-determined time. In the official Evernote client applications, these alerts may be local notifications, icon badges, etc. This will vary by application and will include a daily digest email sent by Evernote with a list of all reminders due that day (provided the user has opted into this feature).Place one or more notes at the top of a list of notes (the contents of a notebook, results of a search, when browsing a tag — basically any instance in which notes are listed). This functionality is controlled by three attributes in the NoteAttributes data structure: reminderTime, reminderOrder and reminderDoneTime. reminderOrder Setting the reminderOrder attribute, a long integer value, accomplishes three things: Sets a reminder on the note that will be synced to Evernote. The latter effect warrants some additional discussion. reminderTime reminderDoneTime Reminder Reordering
Licensing a repository Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software. Choosing the right license We created choosealicense.com, to help you understand how to license your code. You're under no obligation to choose a license. Note: If you publish your source code in a public repository on GitHub, according to the Terms of Service, other GitHub users have the right to view and fork your repository within the GitHub site. Determining the location of your license Most people place their license text in a file named LICENSE.txt (or LICENSE.md) in the root of the repository; here's an example from Hubot. Some projects include information about their license in their README. As a best practice, we encourage you to include the license file with your project. Searching GitHub by license type Detecting a license Disclaimer Further reading
Hyper-Threading on ESX Server Those of us at VMware that regularly engaged with our field or directly with customers are often asked how Hyper-Threading impacts the performance of a system. I've now been asked this question enough times to have my canned "It Depends" response on the tip of my tongue for every conference I present at. I'm going to use this document to elaborate on that point a bit and provide a little more detail. Hyper-Threading is a technology included by Intel first in their Netburst line of parts. Hyper-Threaded processors present their individual processing cores to the system as if they are two processing cores. Hyper-Threading (HT) has been supported in ESX Server since version 2. Understanding HT performance on native systems is tricky enough. The exact gains due to HT even on native systems is dependent on the workload. The best generalizations we can provide about HT on ESX are: Hyper-Threading configuration options for performance optimization were provided in ESX Server 3 and beyond.
A successful Git branching model » nvie.com Note of reflection (March 5, 2020)This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being. In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts — but unfortunately also as a dogma or panacea.During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting more towards web apps — at least in my filter bubble. Web apps are typically continuously delivered, not rolled back, and you don't have to support multiple versions of the software running in the wild.This is not the class of software that I had in mind when I wrote the blog post 10 years ago. Why git? ¶ For a thorough discussion on the pros and cons of Git compared to centralized source code control systems, see the web. The main branches ¶ develop
freeCodeCamp/freeCodeCamp: The open source codebase and curriculum. Learn to code and help nonprofits. Note Links Note Links There are currently three types of links to notes offered by Evernote. Note Links In-App Note Links Public Links Note Links are used to reference a note in a web browser that when the recipient of the link already has access via notebook or individual note sharing. Before we dive into the structure of a link we should first take a look at the components of the links: userID- the ID of the user, it should be stated that unless otherwise noted the user ID referenced below is that of the of the owner of that note. Note Links Note Links are used to reference a note in a browser when the recipient of the link already has access via notebook or individual note sharing. Structure Where: [service] is the name of the Evernote service (either sandbox.evernote.com or www.evernote.com) [userId] is the user ID of the notebook owner [shardId] is the shard ID where the note is stored [noteGuid] is the GUID of the note that is being linked to
Resetting, Checking Out & Reverting The git reset, git checkout, and git revert commands are some of the most useful tools in your Git toolbox. They all let you undo some kind of change in your repository, and the first two commands can be used to manipulate either commits or individual files. Because they’re so similar, it’s very easy to mix up which command should be used in any given development scenario. It helps to think about each command in terms of their effect on the three state management mechanisms of a Git repository: the working directory, the staged snapshot, and the commit history. A checkout is an operation that moves the HEAD ref pointer to a specified commit. This example demonstrates a sequence of commits on the master branch. This is an update to the "Commit History" tree. A revert is an operation that takes a specified commit and creates a new commit which inverses the specified commit. git revert can only be run at a commit level scope and has no file level functionality. Commit Level Operations
Managed, Unmanaged, Native: What Kind of Code Is This? With the release of Visual Studio .NET 2003 (formerly known as Everett) on April 24th, many developers are now willing to consider using the new technology known as managed code. But especially for C++ developers, it can be a bit confusing. That's because C++, as I pointed out in my first column here, is special. What Is Managed Code? Managed Code is what Visual Basic .NET and C# compilers create. Managed code runs in the Common Language Runtime. As the assembly runs, the runtime continues to provide services such as security, memory management, threading, and the like. Visual Basic .NET and C# can produce only managed code. What Is Unmanaged Code? Unmanaged code is what you use to make before Visual Studio .NET 2002 was released. Unlike the other Microsoft languages in Visual Studio, Visual C++ can create unmanaged applications. This can lead to some confusion: When you create a .Managed C++ application., the build product is an assembly of IL with an .exe extension. Foo f; Bar b;
Git Workflows and Tutorials The array of possible workflows can make it hard to know where to begin when implementing Git in the workplace. This page provides a starting point by surveying the most common Git workflows for enterprise teams. As you read through, remember that these workflows are designed to be guidelines rather than concrete rules. Centralized Workflow Transitioning to a distributed version control system may seem like a daunting task, but you don’t have to change your existing workflow to take advantage of Git. However, using Git to power your development workflow presents a few advantages over SVN. Second, it gives you access to Git’s robust branching and merging model. How It Works Like Subversion, the Centralized Workflow uses a central repository to serve as the single point-of-entry for all changes to the project. Developers start by cloning the central repository. To publish changes to the official project, developers “push” their local master branch to the central repository. Example git push
Git Handbook · GitHub Guides What’s a version control system? A version control system, or VCS, tracks the history of changes as people and teams collaborate on projects together. As the project evolves, teams can run tests, fix bugs, and contribute new code with the confidence that any version can be recovered at any time. Developers can review project history to find out: Which changes were made? What’s a distributed version control system? Git is an example of a distributed version control system (DVCS) commonly used for open source and commercial software development. Without version control, team members are subject to redundant tasks, slower timelines, and multiple copies of a single project. Why Git? According to the latest Stack Overflow developer survey, more than 70 percent of developers use Git, making it the most-used VCS in the world. Git lets developers see the entire timeline of their changes, decisions, and progression of any project in one place. What’s a repository? Basic Git commands How GitHub works